[PATCHv2] git-rm.txt: Fix quoting
- From
Michael J Gruber <git@drmicha.warpmail.net>
- Date
- Dec 8, 2010, 11:15 UTC
- Message-ID
- <73d13b752212b557c0dc157edea9a62122840e93.1291806379.git.git@drmicha.warpmail.net>
- In-Reply-To
- <20101207172542.GA25827@sigill.intra.peff.net>
Literal " produces typographically incorrect quotations, but "works" in most circumstances. In the subheadings of git-rm.txt, it "works" for the html backend but not for the docbook conversion to nroff: double "" and spurious double spaces appear in the output.
Replace "incorrect" quotations by ``correct'' ones, and fix other "quotations" which are really 'command names' resp. plain words.
This should make git-rm.txt "-clean.
Reported-by: Jeff King <peff@peff.net> Helped-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
--- While we don't need to match the underlines to the header's length, it looks nicer. So v2 incorporates this and the other changes: - untar is not a command on proper OSs - rsync is not a complete command line (implicit style guide...)
Documentation/git-rm.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/Documentation/git-rm.txt b/Documentation/git-rm.txt index 71e3d9f..0adbe8b 100644 --- a/Documentation/git-rm.txt +++ b/Documentation/git-rm.txt @@ -89,8 +89,8 @@ the paths that have disappeared from the filesystem. However, depending on the use case, there are several ways that can be done. -Using "git commit -a" -~~~~~~~~~~~~~~~~~~~~~ +Using ``git commit -a'' +~~~~~~~~~~~~~~~~~~~~~~~ If you intend that your next commit should record all modifications of tracked files in the working tree and record all removals of files that have been removed from the working tree with `rm` @@ -98,8 +98,8 @@ files that have been removed from the working tree with `rm` automatically notice and record all removals. You can also have a similar effect without committing by using `git add -u`. -Using "git add -A" -~~~~~~~~~~~~~~~~~~ +Using ``git add -A'' +~~~~~~~~~~~~~~~~~~~~ When accepting a new code drop for a vendor branch, you probably want to record both the removal of paths and additions of new paths as well as modifications of existing paths. @@ -111,8 +111,8 @@ tree using this command: git ls-files -z | xargs -0 rm -f ---------------- -and then "untar" the new code in the working tree. Alternately -you could "rsync" the changes into the working tree. +and then untar the new code in the working tree. Alternately +you could 'rsync' the changes into the working tree. After that, the easiest way to record all removals, additions, and modifications in the working tree is:
-- 1.7.3.2.662.g6fd5b8.dirty