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-send-pack.txt | |
parent | ca768288b650a4929bc1d58783a929a9a792e30e (diff) | |
download | git-0b444cdb19bcfcc7f59b7b00783cbfbbc5ddcf63.tar.gz |
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-send-pack.txt')
-rw-r--r-- | Documentation/git-send-pack.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-send-pack.txt b/Documentation/git-send-pack.txt index 5a04c6eaf7..8178d92642 100644 --- a/Documentation/git-send-pack.txt +++ b/Documentation/git-send-pack.txt @@ -12,7 +12,7 @@ SYNOPSIS DESCRIPTION ----------- -Usually you would want to use 'git-push', which is a +Usually you would want to use 'git push', which is a higher-level wrapper of this command, instead. See linkgit:git-push[1]. Invokes 'git-receive-pack' on a possibly remote repository, and @@ -86,7 +86,7 @@ and the destination side (after the colon). The ref to be pushed is determined by finding a match that matches the source side, and where it is pushed is determined by using the destination side. The rules used to match a ref are the same -rules used by 'git-rev-parse' to resolve a symbolic ref +rules used by 'git rev-parse' to resolve a symbolic ref name. See linkgit:git-rev-parse[1]. - It is an error if <src> does not match exactly one of the |