summaryrefslogtreecommitdiffstats
path: root/technical/hash-function-transition.txt
diff options
context:
space:
mode:
Diffstat (limited to 'technical/hash-function-transition.txt')
-rw-r--r--technical/hash-function-transition.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/technical/hash-function-transition.txt b/technical/hash-function-transition.txt
index e2ac36dd2..ed5748108 100644
--- a/technical/hash-function-transition.txt
+++ b/technical/hash-function-transition.txt
@@ -562,7 +562,7 @@ hash re-encode during clone and to encourage peers to modernize.
The design described here allows fetches by SHA-1 clients of a
personal SHA-256 repository because it's not much more difficult than
allowing pushes from that repository. This support needs to be guarded
-by a configuration option --- servers like git.kernel.org that serve a
+by a configuration option -- servers like git.kernel.org that serve a
large number of clients would not be expected to bear that cost.
Meaning of signatures