diff options
| author | Nicholas Johnson <nick@nicholasjohnson.ch> | 2023-08-31 00:00:00 +0000 |
|---|---|---|
| committer | Nicholas Johnson <nick@nicholasjohnson.ch> | 2023-09-01 00:00:00 +0000 |
| commit | b7f7dad048c9568870b2045d0fa67f08c30a42cf0e55abc743672d292c517dfd (patch) | |
| tree | 2e89595bfcd65d342cfbeff7e9b0e751b5709e4fa4bd21a29cbd8e33e9917dd0 | |
| parent | 195353bd1f9762b3b9c9846bac1f51c53ce5b2bcbb13db3a1aa6c1dc4e828122 (diff) | |
Replace Git mailing list link with Git Rev News
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -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. 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. +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 [a writeup of the discussion](https://git.github.io/rev_news/2023/08/31/edition-102/#support) from the 102nd edition of Git Rev News. ## License |