Documentation: prepare to be consistent about "git-" versus "git "
With the dashed forms of git commands not in $(bindir), we have to change many instances of "git-command" to "git command". Also, for consistency it is at times appropriate to make the opposite change. In some cases, the change is not so simple as changing one character. This patch gets rid of some of those cases by rewrapping lines. Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jonathan Nieder committed
Jun 30, 2008 at 17:17 UTC
46e56e81b3bc91af7071809fbda8dcdec22c4cb1
4 files changed
+10
-10
Documentation/git-mailinfo.txt
+2
-2
@@ -29,8 +29,8 @@ OPTIONS
29
among which (1) remove 'Re:' or 're:', (2) leading
30
whitespaces, (3) '[' up to ']', typically '[PATCH]', and
31
then prepends "[PATCH] ". This flag forbids this
32
- munging, and is most useful when used to read back 'git
33
- format-patch -k' output.
32
+ munging, and is most useful when used to read back
33
+ 'git format-patch -k' output.
34
35
-u::
36
The commit log message, author name and author email are
Documentation/git-tag.txt
+2
-2
@@ -122,8 +122,8 @@ others have already seen the old one. So just use "git tag -f"
122
again, as if you hadn't already published the old one.
123
124
However, Git does *not* (and it should not) change tags behind
125
-users back. So if somebody already got the old tag, doing a "git
126
-pull" on your tree shouldn't just make them overwrite the old
125
+users back. So if somebody already got the old tag, doing a
126
+"git pull" on your tree shouldn't just make them overwrite the old
127
one.
128
129
If somebody got a release tag from you, you cannot just change
Documentation/gitrepository-layout.txt
+4
-4
@@ -167,14 +167,14 @@ info/grafts::
167
info/exclude::
168
This file, by convention among Porcelains, stores the
169
exclude pattern list. `.gitignore` is the per-directory
170
- ignore file. `git status`, `git add`, `git rm` and `git
171
- clean` look at it but the core git commands do not look
170
+ ignore file. `git status`, `git add`, `git rm` and
171
+ `git clean` look at it but the core git commands do not look
172
at it. See also: linkgit:gitignore[5].
173
174
remotes::
175
Stores shorthands to be used to give URL and default
176
- refnames to interact with remote repository to `git
177
- fetch`, `git pull` and `git push` commands.
176
+ refnames to interact with remote repository to
177
+ `git fetch`, `git pull` and `git push` commands.
178
179
logs::
180
Records of changes made to refs are stored in this
Documentation/gittutorial.txt
+2
-2
@@ -19,8 +19,8 @@ If you are instead primarily interested in using git to fetch a project,
19
for example, to test the latest version, you may prefer to start with
20
the first two chapters of link:user-manual.html[The Git User's Manual].
21
22
-First, note that you can get documentation for a command such as "git
23
-log --graph" with:
22
+First, note that you can get documentation for a command such as
23
+"git log --graph" with:
24
25
------------------------------------------------
26
$ man git-log