From 46e56e81b3bc91af7071809fbda8dcdec22c4cb1 Mon Sep 17 00:00:00 2001 From: Jonathan Nieder Date: Mon, 30 Jun 2008 17:17:07 -0500 Subject: 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 Signed-off-by: Junio C Hamano diff --git a/Documentation/git-mailinfo.txt b/Documentation/git-mailinfo.txt index 183dc1d..6a73b73 100644 --- a/Documentation/git-mailinfo.txt +++ b/Documentation/git-mailinfo.txt @@ -29,8 +29,8 @@ OPTIONS among which (1) remove 'Re:' or 're:', (2) leading whitespaces, (3) '[' up to ']', typically '[PATCH]', and then prepends "[PATCH] ". This flag forbids this - munging, and is most useful when used to read back 'git - format-patch -k' output. + munging, and is most useful when used to read back + 'git format-patch -k' output. -u:: The commit log message, author name and author email are diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt index 8f40f4b..0c41711 100644 --- a/Documentation/git-tag.txt +++ b/Documentation/git-tag.txt @@ -122,8 +122,8 @@ others have already seen the old one. So just use "git tag -f" again, as if you hadn't already published the old one. However, Git does *not* (and it should not) change tags behind -users back. So if somebody already got the old tag, doing a "git -pull" on your tree shouldn't just make them overwrite the old +users back. So if somebody already got the old tag, doing a +"git pull" on your tree shouldn't just make them overwrite the old one. If somebody got a release tag from you, you cannot just change diff --git a/Documentation/gitrepository-layout.txt b/Documentation/gitrepository-layout.txt index b75508a..2afc5a3 100644 --- a/Documentation/gitrepository-layout.txt +++ b/Documentation/gitrepository-layout.txt @@ -167,14 +167,14 @@ info/grafts:: info/exclude:: This file, by convention among Porcelains, stores the exclude pattern list. `.gitignore` is the per-directory - ignore file. `git status`, `git add`, `git rm` and `git - clean` look at it but the core git commands do not look + ignore file. `git status`, `git add`, `git rm` and + `git clean` look at it but the core git commands do not look at it. See also: linkgit:gitignore[5]. remotes:: Stores shorthands to be used to give URL and default - refnames to interact with remote repository to `git - fetch`, `git pull` and `git push` commands. + refnames to interact with remote repository to + `git fetch`, `git pull` and `git push` commands. logs:: Records of changes made to refs are stored in this diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt index b833167..144bacd 100644 --- a/Documentation/gittutorial.txt +++ b/Documentation/gittutorial.txt @@ -19,8 +19,8 @@ If you are instead primarily interested in using git to fetch a project, for example, to test the latest version, you may prefer to start with the first two chapters of link:user-manual.html[The Git User's Manual]. -First, note that you can get documentation for a command such as "git -log --graph" with: +First, note that you can get documentation for a command such as +"git log --graph" with: ------------------------------------------------ $ man git-log -- cgit v0.10.2-6-g49f6