El 21/1/2009, a las 21:54, Junio C Hamano escribió:
Felipe Contreras <felipe.contreras@xxxxxxxxx> writes:
This is shorter, avoids the burder to think about the format of the
configuration file, and git config is already used in other places in
the manual.
I am moderately against changing this part to use "git config".
We traditionally introduced how to set configuration variables first
by
editing it in an editor, and this was quite deliberate, in order to
show
how the configuration file looks like, to demonstrate that there is no
deep magic in the file format, and to explain that it is perfectly
Ok to
edit it without using "git config" command.
If that's the goal, why not do both?:
1. Show people how to use "git config" like this patch does (seeing as
it's easier and less error prone)
2. Tell people that they can inspect and even edit the config file by
hand if they want
The actual order of 1 and 2 depends on where you want to place more
emphasis:
Something like either:
Before creating any commits, you should introduce yourself to git.
The
easiest way to do so is to make sure the following lines appear in a
file named .gitconfig in your home directory:
[user]
name = Your Name Comes Here
email = you@xxxxxxxxxxxxxxxxxxxxxx
As a convenience you can use linkgit:git-config[1] to modify
your .gitconfig
instead of editing it by hand:
$ git config --global user.name "Your Name Comes Here"
$ git config --global user.email you@xxxxxxxxxxxxxxxxxxxxxx
Or:
Before creating any commits, you should introduce yourself to git.
The
easiest way is to use the linkgit:git-config[1] command:
$ git config --global user.name "Your Name Comes Here"
$ git config --global user.email you@xxxxxxxxxxxxxxxxxxxxxx
Your settings are written to a file named .gitconfig in your home
directory which you can inspect or even edit by hand. Settings look
like this:
[user]
name = Your Name Comes Here
email = you@xxxxxxxxxxxxxxxxxxxxxx
Cheers,
Wincent
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
