diff options
author | Thomas Rast <trast@student.ethz.ch> | 2010-01-10 00:33:00 +0100 |
---|---|---|
committer | Thomas Rast <trast@student.ethz.ch> | 2010-01-10 13:01:28 +0100 |
commit | 0b444cdb19bcfcc7f59b7b00783cbfbbc5ddcf63 (patch) | |
tree | fbc79ccb4f6e809a560bd807c4a17dd6e6681161 /Documentation/git-patch-id.txt | |
parent | ca768288b650a4929bc1d58783a929a9a792e30e (diff) | |
download | git-0b444cdb19bcfcc7f59b7b00783cbfbbc5ddcf63.tar.gz git-0b444cdb19bcfcc7f59b7b00783cbfbbc5ddcf63.tar.xz |
Documentation: spell 'git cmd' without dash throughout
The documentation was quite inconsistent when spelling 'git cmd' if it
only refers to the program, not to some specific invocation syntax:
both 'git-cmd' and 'git cmd' spellings exist.
The current trend goes towards dashless forms, and there is precedent
in 647ac70 (git-svn.txt: stop using dash-form of commands.,
2009-07-07) to actively eliminate the dashed variants.
Replace 'git-cmd' with 'git cmd' throughout, except where git-shell,
git-cvsserver, git-upload-pack, git-receive-pack, and
git-upload-archive are concerned, because those really live in the
$PATH.
Diffstat (limited to 'Documentation/git-patch-id.txt')
-rw-r--r-- | Documentation/git-patch-id.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-patch-id.txt b/Documentation/git-patch-id.txt index 253fc0fc2..4dae1390a 100644 --- a/Documentation/git-patch-id.txt +++ b/Documentation/git-patch-id.txt @@ -18,7 +18,7 @@ ID" are almost guaranteed to be the same thing. IOW, you can use this thing to look for likely duplicate commits. -When dealing with 'git-diff-tree' output, it takes advantage of +When dealing with 'git diff-tree' output, it takes advantage of the fact that the patch is prefixed with the object name of the commit, and outputs two 40-byte hexadecimal strings. The first string is the patch ID, and the second string is the commit ID. |