aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicholasjohnson.ch>2023-08-04 00:00:00 +0000
committerNicholas Johnson <nick@nicholasjohnson.ch>2023-08-04 00:00:00 +0000
commit195353bd1f9762b3b9c9846bac1f51c53ce5b2bcbb13db3a1aa6c1dc4e828122 (patch)
tree841fbde7718a6333cd355556a8e87b5532db3e5c60fe3d39895a79373f0f4889
parentb06a3ef986a7d856e6cdec6f05652ac8217b307ab56773576d952d95c68376e2 (diff)
Mention correspondence with Git developers
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index a0f176f..a3ebe76 100644
--- a/README.md
+++ b/README.md
@@ -71,7 +71,7 @@ The last step is to set the script as executable with `chmod +x /path/to/custom-
Github is known to record [when commits are pushed](https://api.github.com/repos/cirosantilli/china-dictatorship/events). See the ticket about [Github contribution activity](https://github.com/isaacs/github/issues/142). To obfuscate push times, one could push code with cron at regular time intervals.
-It's possible to use Git hooks to accomplish timestamp obfuscation, but it's still necessary to manually override the date for some Git commands, making it very inconvenient. The developers of Git should make timestamp obfuscation a feature in order to make doing all this unnecessary.
+It's possible to use Git hooks to accomplish timestamp obfuscation, but it's still necessary to manually override the date for some Git commands, making it very inconvenient. I asked Git developers to implement a timestamp privacy feature, but it was decided against. If you're curious why, here's [the relevant thread](https://lore.kernel.org/git/CTZ9RD9RQ5UO.3OIJX50PKMIR0@anonymous/t/#u) on Git's public mailing list.
## License