Skip to content

Commit 0448352

Browse files
jnarebJunio C Hamano
authored andcommitted
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 <[email protected]> Acked-by: J. Bruce Fields <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent bbf4b41 commit 0448352

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

Documentation/user-manual.txt

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ $ git branch -r # list
8484
origin/master
8585
origin/next
8686
...
87-
$ git branch checkout -b masterwork origin/master
87+
$ git checkout -b masterwork origin/master
8888
-----------------------------------------------
8989

9090
Fetch a branch from a different repository, and give it a new
@@ -155,8 +155,8 @@ Make sure git knows who to blame:
155155
------------------------------------------------
156156
$ cat >~/.gitconfig <<\EOF
157157
[user]
158-
name = Your Name Comes Here
159-
158+
name = Your Name Comes Here
159+
160160
EOF
161161
------------------------------------------------
162162

@@ -195,7 +195,7 @@ Importing or exporting patches:
195195
-----------------------------------------------
196196
$ git format-patch origin..HEAD # format a patch for each commit
197197
# 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"
199199
-----------------------------------------------
200200

201201
Fetch a branch in a different git repository, then merge into the
@@ -579,7 +579,7 @@ cloned from, using gitlink:git-remote[1]:
579579

580580
-------------------------------------------------
581581
$ git remote add linux-nfs git://linux-nfs.org/pub/nfs-2.6.git
582-
$ git fetch
582+
$ git fetch linux-nfs
583583
* refs/remotes/linux-nfs/master: storing branch 'master' ...
584584
commit: bf81b46
585585
-------------------------------------------------
@@ -680,7 +680,7 @@ occasionally you may land on a commit that broke something unrelated;
680680
run
681681

682682
-------------------------------------------------
683-
$ git bisect-visualize
683+
$ git bisect visualize
684684
-------------------------------------------------
685685

686686
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
765765
running
766766

767767
-------------------------------------------------
768-
$ git-tag stable-1 1b2e1d63ff
768+
$ git tag stable-1 1b2e1d63ff
769769
-------------------------------------------------
770770

771771
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
909909
descendants:
910910

911911
-------------------------------------------------
912-
$ git name-rev e05db0fd
912+
$ git name-rev --tags e05db0fd
913913
e05db0fd tags/v1.5.0-rc1^0~23
914914
-------------------------------------------------
915915

@@ -918,7 +918,7 @@ revision using a tag on which the given commit is based:
918918

919919
-------------------------------------------------
920920
$ git describe e05db0fd
921-
v1.5.0-rc0-ge05db0f
921+
v1.5.0-rc0-260-ge05db0f
922922
-------------------------------------------------
923923

924924
but that may sometimes help you guess which tags might come after the
@@ -1861,7 +1861,7 @@ Allow web browsing of a repository
18611861

18621862
The gitweb cgi script provides users an easy way to browse your
18631863
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.
18651865

18661866
Examples
18671867
--------

0 commit comments

Comments
 (0)