Documentation: A few minor fixes to Git User's Manual
Mainly consistent usage of "git command" and not "git-command" syntax Signed-off-by: Jakub Narebski <jnareb@gmail.com> Acked-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by: Junio C Hamano <junkio@cox.net>
Jakub Narebski committed
Apr 3, 2007 at 18:27 UTC
04483524ecfe67e4d4f120b0bf6d91b43a02d40a
1 file changed
+10
-10
Documentation/user-manual.txt
+10
-10
@@ -84,7 +84,7 @@ $ git branch -r # list
84
origin/master
85
origin/next
86
...
87
-$ git branch checkout -b masterwork origin/master
87
+$ git checkout -b masterwork origin/master
88
-----------------------------------------------
89
90
Fetch a branch from a different repository, and give it a new
@@ -155,8 +155,8 @@ Make sure git knows who to blame:
155
------------------------------------------------
156
$ cat >~/.gitconfig <<\EOF
157
[user]
158
-name = Your Name Comes Here
159
-email = you@yourdomain.example.com
158
+ name = Your Name Comes Here
159
+ email = you@yourdomain.example.com
160
EOF
161
------------------------------------------------
162
@@ -195,7 +195,7 @@ Importing or exporting patches:
195
-----------------------------------------------
196
$ git format-patch origin..HEAD # format a patch for each commit
197
# in HEAD but not in origin
198
-$ git-am mbox # import patches from the mailbox "mbox"
198
+$ git am mbox # import patches from the mailbox "mbox"
199
-----------------------------------------------
200
201
Fetch a branch in a different git repository, then merge into the
@@ -579,7 +579,7 @@ cloned from, using gitlink:git-remote[1]:
579
580
-------------------------------------------------
581
$ git remote add linux-nfs git://linux-nfs.org/pub/nfs-2.6.git
582
-$ git fetch
582
+$ git fetch linux-nfs
583
* refs/remotes/linux-nfs/master: storing branch 'master' ...
584
commit: bf81b46
585
-------------------------------------------------
@@ -680,7 +680,7 @@ occasionally you may land on a commit that broke something unrelated;
680
run
681
682
-------------------------------------------------
683
-$ git bisect-visualize
683
+$ git bisect visualize
684
-------------------------------------------------
685
686
which will run gitk and label the commit it chose with a marker that
@@ -765,7 +765,7 @@ We can also create a tag to refer to a particular commit; after
765
running
766
767
-------------------------------------------------
768
-$ git-tag stable-1 1b2e1d63ff
768
+$ git tag stable-1 1b2e1d63ff
769
-------------------------------------------------
770
771
You can use stable-1 to refer to the commit 1b2e1d63ff.
@@ -909,7 +909,7 @@ name based on any tag it finds pointing to one of the commit's
909
descendants:
910
911
-------------------------------------------------
912
-$ git name-rev e05db0fd
912
+$ git name-rev --tags e05db0fd
913
e05db0fd tags/v1.5.0-rc1^0~23
914
-------------------------------------------------
915
@@ -918,7 +918,7 @@ revision using a tag on which the given commit is based:
918
919
-------------------------------------------------
920
$ git describe e05db0fd
921
-v1.5.0-rc0-ge05db0f
921
+v1.5.0-rc0-260-ge05db0f
922
-------------------------------------------------
923
924
but that may sometimes help you guess which tags might come after the
@@ -1861,7 +1861,7 @@ Allow web browsing of a repository
1861
1862
The gitweb cgi script provides users an easy way to browse your
1863
project's files and history without having to install git; see the file
1864
-gitweb/README in the git source tree for instructions on setting it up.
1864
+gitweb/INSTALL in the git source tree for instructions on setting it up.
1865
1866
Examples
1867
--------