git-add/rm doc: Consistently back-quote
Consistently back-quote commands, options and file names. Signed-off-by: Björn Gustavsson <bgustavsson@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Björn Gustavsson committed
Dec 7, 2009 at 19:26 UTC
441947f6d7533e7567f8ad02fafbf36c22a5ddf9
2 files changed
+15
-15
Documentation/git-add.txt
+12
-12
@@ -24,22 +24,22 @@ remove paths that do not exist in the working tree anymore.
24
The "index" holds a snapshot of the content of the working tree, and it
25
is this snapshot that is taken as the contents of the next commit. Thus
26
after making any changes to the working directory, and before running
27
-the commit command, you must use the 'add' command to add any new or
27
+the commit command, you must use the `add` command to add any new or
28
modified files to the index.
29
30
This command can be performed multiple times before a commit. It only
31
adds the content of the specified file(s) at the time the add command is
32
run; if you want subsequent changes included in the next commit, then
33
-you must run 'git add' again to add the new content to the index.
33
+you must run `git add` again to add the new content to the index.
34
35
-The 'git status' command can be used to obtain a summary of which
35
+The `git status` command can be used to obtain a summary of which
36
files have changes that are staged for the next commit.
37
38
-The 'git add' command will not add ignored files by default. If any
39
-ignored files were explicitly specified on the command line, 'git add'
38
+The `git add` command will not add ignored files by default. If any
39
+ignored files were explicitly specified on the command line, `git add`
40
will fail with a list of ignored files. Ignored files reached by
41
directory recursion or filename globbing performed by Git (quote your
42
-globs before the shell) will be silently ignored. The 'add' command can
42
+globs before the shell) will be silently ignored. The `add` command can
43
be used to add ignored files with the `-f` (force) option.
44
45
Please see linkgit:git-commit[1] for alternative ways to add content to a
@@ -119,8 +119,8 @@ subdirectories.
119
Record only the fact that the path will be added later. An entry
120
for the path is placed in the index with no content. This is
121
useful for, among other things, showing the unstaged content of
122
- such files with 'git diff' and committing them with 'git commit
123
- -a'.
122
+ such files with `git diff` and committing them with `git commit
123
+ -a`.
124
125
--refresh::
126
Don't add the file(s), but only refresh their stat()
@@ -140,7 +140,7 @@ subdirectories.
140
Configuration
141
-------------
142
143
-The optional configuration variable 'core.excludesfile' indicates a path to a
143
+The optional configuration variable `core.excludesfile` indicates a path to a
144
file containing patterns of file names to exclude from git-add, similar to
145
$GIT_DIR/info/exclude. Patterns in the exclude file are used in addition to
146
those in info/exclude. See linkgit:gitrepository-layout[5].
@@ -188,7 +188,7 @@ and type return, like this:
188
What now> 1
189
------------
190
191
-You also could say "s" or "sta" or "status" above as long as the
191
+You also could say `s` or `sta` or `status` above as long as the
192
choice is unique.
193
194
The main command loop has 6 subcommands (plus help and quit).
@@ -196,9 +196,9 @@ The main command loop has 6 subcommands (plus help and quit).
196
status::
197
198
This shows the change between HEAD and index (i.e. what will be
199
- committed if you say "git commit"), and between index and
199
+ committed if you say `git commit`), and between index and
200
working tree files (i.e. what you could stage further before
201
- "git commit" using "git-add") for each path. A sample output
201
+ `git commit` using `git add`) for each path. A sample output
202
looks like this:
203
+
204
------------
Documentation/git-rm.txt
+3
-3
@@ -12,13 +12,13 @@ SYNOPSIS
12
DESCRIPTION
13
-----------
14
Remove files from the index, or from the working tree and the index.
15
-'git-rm' will not remove a file from just your working directory.
15
+`git rm` will not remove a file from just your working directory.
16
(There is no option to remove a file only from the work tree
17
and yet keep it in the index; use `/bin/rm` if you want to do that.)
18
The files being removed have to be identical to the tip of the branch,
19
and no updates to their contents can be staged in the index,
20
though that default behavior can be overridden with the `-f` option.
21
-When '--cached' is given, the staged content has to
21
+When `--cached` is given, the staged content has to
22
match either the tip of the branch or the file on disk,
23
allowing the file to be removed from just the index.
24
@@ -64,7 +64,7 @@ OPTIONS
64
65
-q::
66
--quiet::
67
- 'git-rm' normally outputs one line (in the form of an "rm" command)
67
+ `git rm` normally outputs one line (in the form of an `rm` command)
68
for each file removed. This option suppresses that output.
69
70