summaryrefslogtreecommitdiff
path: root/Documentation/gitdiffcore.txt
diff options
context:
space:
mode:
authorLibravatar Thomas Ackermann <th.acker@arcor.de>2013-04-15 19:49:04 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-04-15 11:08:37 -0700
commitd5fa1f1a69f578831179b77893aac480b986e875 (patch)
tree1e04ba1f10d79969f18cb62d2a30844e98256b02 /Documentation/gitdiffcore.txt
parentglossary: improve description of SHA-1 related topics (diff)
downloadtgif-d5fa1f1a69f578831179b77893aac480b986e875.tar.xz
The name of the hash function is "SHA-1", not "SHA1"
Use "SHA-1" instead of "SHA1" whenever we talk about the hash function. When used as a programming symbol, we keep "SHA1". Signed-off-by: Thomas Ackermann <th.acker@arcor.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/gitdiffcore.txt')
-rw-r--r--Documentation/gitdiffcore.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/gitdiffcore.txt b/Documentation/gitdiffcore.txt
index 4ed71c76cb..568d75783a 100644
--- a/Documentation/gitdiffcore.txt
+++ b/Documentation/gitdiffcore.txt
@@ -108,7 +108,7 @@ it changes it to:
For the purpose of breaking a filepair, diffcore-break examines
the extent of changes between the contents of the files before
and after modification (i.e. the contents that have "bcd1234..."
-and "0123456..." as their SHA1 content ID, in the above
+and "0123456..." as their SHA-1 content ID, in the above
example). The amount of deletion of original contents and
insertion of new material are added together, and if it exceeds
the "break score", the filepair is broken into two. The break