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-clean.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-clean.txt')
-rw-r--r-- | Documentation/git-clean.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-clean.txt b/Documentation/git-clean.txt index 9d291bdd26..335c885bb7 100644 --- a/Documentation/git-clean.txt +++ b/Documentation/git-clean.txt @@ -34,7 +34,7 @@ OPTIONS -f:: --force:: If the git configuration specifies clean.requireForce as true, - 'git-clean' will refuse to run unless given -f or -n. + 'git clean' will refuse to run unless given -f or -n. -n:: --dry-run:: @@ -48,7 +48,7 @@ OPTIONS -x:: Don't use the ignore rules. This allows removing all untracked files, including build products. This can be used (possibly in - conjunction with 'git-reset') to create a pristine + conjunction with 'git reset') to create a pristine working directory to test a clean build. -X:: |