aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicholasjohnson.ch>2023-07-17 00:00:00 +0000
committerNicholas Johnson <nick@nicholasjohnson.ch>2023-07-17 00:00:00 +0000
commitb06a3ef986a7d856e6cdec6f05652ac8217b307ab56773576d952d95c68376e2 (patch)
tree2f6d99e879999ad1176a3a5292678b99903d3a566800452f6fb6e45c352834ed
parent9acac87485de47a1d8de704e6f49ecb79da5cff92b80dc5797d5bdd0ac452059 (diff)
downloadgit-privacy-b06a3ef986a7d856e6cdec6f05652ac8217b307ab56773576d952d95c68376e2.tar.gz
git-privacy-b06a3ef986a7d856e6cdec6f05652ac8217b307ab56773576d952d95c68376e2.zip
Add warning
-rw-r--r--README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index a49ac3c..a0f176f 100644
--- a/README.md
+++ b/README.md
@@ -23,6 +23,12 @@ Annotated [Git tag objects](https://git-scm.com/docs/user-manual.html#tag-object
There is another timestamp which comes from the optional GnuPG signature on a commit or annotated tag. It is controlled by GnuPG.
+### ⚠ Warning ⚠
+
+Before you follow any of the steps below to obfuscate Git timestamps, be aware that it can cause certain features of Git to break in unexpected ways. The author takes no responsibility for any breakage that occurs.
+
+The author is not a lawyer and this is not legal advice, but obfuscating Git's timestamps may also result in more difficulty refuting copyright claims. The author takes no responsibility for this either.
+
### Obfuscating Timestamps for Commits and Annotated Tags
Git can't remove timestamps altogether, but the `GIT_AUTHOR_DATE` and `GIT_COMMITTER_DATE` environment variables can be set to any arbitrary date. Preferably, use dates from before Git was invented to clearly signal the timestamps are forged: