diff options
| author | Thomas Ackermann <th.acker@arcor.de> | 2013-04-15 19:49:04 +0200 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2013-04-15 11:08:37 -0700 |
| commit | d5fa1f1a69f578831179b77893aac480b986e875 (patch) | |
| tree | 1e04ba1f10d79969f18cb62d2a30844e98256b02 /Documentation/revisions.txt | |
| parent | 3ab501209b46e83a377ac5a781a8f2fef7f4f30c (diff) | |
| download | git-d5fa1f1a69f578831179b77893aac480b986e875.tar.gz | |
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/revisions.txt')
| -rw-r--r-- | Documentation/revisions.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt index b0f72206a0..c5822634fc 100644 --- a/Documentation/revisions.txt +++ b/Documentation/revisions.txt @@ -2,13 +2,13 @@ SPECIFYING REVISIONS -------------------- A revision parameter '<rev>' typically, but not necessarily, names a -commit object. It uses what is called an 'extended SHA1' +commit object. It uses what is called an 'extended SHA-1' syntax. Here are various ways to spell object names. The ones listed near the end of this list name trees and blobs contained in a commit. '<sha1>', e.g. 'dae86e1950b1277e545cee180551750029cfe735', 'dae86e':: - The full SHA1 object name (40-byte hexadecimal string), or + The full SHA-1 object name (40-byte hexadecimal string), or a leading substring that is unique within the repository. E.g. dae86e1950b1277e545cee180551750029cfe735 and dae86e both name the same commit object if there is no other object in |