aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Johnson <nicholasjohnson@posteo.org>2021-03-19 00:00:00 +0000
committerNicholas Johnson <nicholasjohnson@posteo.org>2021-03-19 00:00:00 +0000
commit04e8101328809230ab931b24676e5740fd9eed9755c7ea9ab81069550c7642ef (patch)
treef670408cd6f0abb4c20debb28f980f0063e8c13e2c3849a93dc4a5b96d9be15f
parent2c11e656f6e0d803336cfb4f574574476b82d7a5d7ebf3be7ea91d9ee60a4db7 (diff)
downloadgit-privacy-04e8101328809230ab931b24676e5740fd9eed9755c7ea9ab81069550c7642ef.tar.gz
git-privacy-04e8101328809230ab931b24676e5740fd9eed9755c7ea9ab81069550c7642ef.zip
Improve formatting
-rw-r--r--README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index 22d8cb2..0b27b4b 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@
## ❌ Default Git Privacy ❌
Git has a _major_ privacy problem. With only 3 commands _anyone_ can find out the times and dates (down to the second) someone worked on their Git repo.
-```
+```bash
git clone <target-repo>
cd <target-repo>
git log --format=fuller
@@ -75,7 +75,7 @@ chmod +x <path>/gpg2-git
Finally, to make Git use the new gpg2-git program, add the following lines to `~/.gitconfig`:
-```
+```text
[gpg]
program = gpg2-git
```
@@ -92,4 +92,4 @@ The easiest way to resolve this is _don't push any code manually_. Instead use a
Environment variables may seem a very _crude_ way to obfuscate Git timestamps. It's possible to use Git hooks to accomplish timestamp obfuscation, but it doesn't work very well since it's still necessary to manually override the date for some Git commands. Git developers need to make timestamp obfuscation a feature of Git to finally resolve the privacy problem.
## License
-This README file is also licensed under [CC-BY-SA 4.0](LICENSE.txt).
+This README file is licensed under [CC-BY-SA 4.0](LICENSE.txt).