summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 5972304)
raw | patch | inline | side by side (parent: 5972304)
author | J. Bruce Fields <bfields@citi.umich.edu> | |
Mon, 7 May 2007 04:16:33 +0000 (00:16 -0400) | ||
committer | J. Bruce Fields <bfields@citi.umich.edu> | |
Mon, 7 May 2007 05:03:53 +0000 (01:03 -0400) |
Santi Béjar points out that when telling people how to "introduce
themselves" to git we're advising them to replace their entire
.gitconfig file. Fix that.
Cc: "Santi Béjar <sbejar@gmail.com>
Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
themselves" to git we're advising them to replace their entire
.gitconfig file. Fix that.
Cc: "Santi Béjar <sbejar@gmail.com>
Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
Documentation/user-manual.txt | patch | blob | history |
index 03206c53442bb0de757eaabc5cd20fd263f5db95..c292b4d7979320660eff7f6688b08693eb88b408 100644 (file)
Make sure git knows who to blame:
------------------------------------------------
-$ cat >~/.gitconfig <<\EOF
+$ cat >>~/.gitconfig <<\EOF
[user]
name = Your Name Comes Here
email = you@yourdomain.example.com
---------------------
Before creating any commits, you should introduce yourself to git. The
-easiest way to do so is:
+easiest way to do so is to make sure the following lines appear in a
+file named .gitconfig in your home directory:
------------------------------------------------
-$ cat >~/.gitconfig <<\EOF
[user]
name = Your Name Comes Here
email = you@yourdomain.example.com
-EOF
------------------------------------------------
(See the "CONFIGURATION FILE" section of gitlink:git-config[1] for