This is more of a documentation issue.
The new docpatch version supports using the original law dates as commit dates, but there is a slight problem, when the date is older than the UNIX epoch. Git allows to commit that, but it can only be pushed, if allowed in the settings of the receiving repo. Usually pushing fails with something like
remote: error: object 19c480cbd0bef0d9c6e608ececbc062dfb30be9e: badDateOverflow: invalid author/committer line - date causes integer overflow
remote: fatal: Error in object
error: unpack failed: index-pack abnormal exit
To xyz:abc/grundgesetz.git
! [remote rejected] master -> master (unpacker error)
error: Fehler beim Versenden einiger Referenzen nach 'xyz:abc/grundgesetz.git'
But using the entry
[receive "fsck"]
missingEmail = ignore
badDateOverflow = warn
in the .git/config file of the receiving repository (as documented here: https://github.com/git/git/blob/master/Documentation/config.txt#L2783) allows to push.
The result in the Gitlab web looks like this:
Gitlab omnibus has those config files at /var/opt/gitlab/git-data/repositories/[GROUP]/[REPO].git/config, Github seems to have no way to access them.
This is more of a documentation issue.
The new docpatch version supports using the original law dates as commit dates, but there is a slight problem, when the date is older than the UNIX epoch. Git allows to commit that, but it can only be pushed, if allowed in the settings of the receiving repo. Usually pushing fails with something like
But using the entry
in the .git/config file of the receiving repository (as documented here: https://github.com/git/git/blob/master/Documentation/config.txt#L2783) allows to push.
The result in the Gitlab web looks like this:
Gitlab omnibus has those config files at
/var/opt/gitlab/git-data/repositories/[GROUP]/[REPO].git/config, Github seems to have no way to access them.