From: "J. Bruce Fields" <bfields@fieldses.org>
To: Johan Herland <johan@herland.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] user-manual: Use "git config --global" instead of editing ~/.gitconfig
Date: Thu, 10 May 2007 18:02:53 -0400 [thread overview]
Message-ID: <20070510220253.GZ13719@fieldses.org> (raw)
In-Reply-To: <200705102353.31821.johan@herland.net>
On Thu, May 10, 2007 at 11:53:31PM +0200, Johan Herland wrote:
> Use git-config for setting global user.name and user.email rather than
> telling the user to edit ~/.gitconfig directly. This brings
> user-manual.txt in line with tutorial.txt.
The inconsistency is intentional. We want users to know about
git-config, because it's helpful when writing scripts, and because it
has a useful manpage. But we also want them to know about the
config-file syntax, since most of us find reading and editing a file
more intuitive than running git-config. So we use a mixture of both.
--b.
> Signed-off-by: Johan Herland <johan@herland.net>
> ---
> Documentation/user-manual.txt | 7 ++-----
> 1 files changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/user-manual.txt
> b/Documentation/user-manual.txt
> index 13db969..23e2f45 100644
> --- a/Documentation/user-manual.txt
> +++ b/Documentation/user-manual.txt
> @@ -158,11 +158,8 @@ Making changes
> Make sure git knows who to blame:
>
> ------------------------------------------------
> -$ cat >>~/.gitconfig <<\EOF
> -[user]
> - name = Your Name Comes Here
> - email = you@yourdomain.example.com
> -EOF
> +$ git config --global user.name "Your Name Comes Here"
> +$ git config --global user.email you@yourdomain.example.com
> ------------------------------------------------
>
> Select file contents to include in the next commit, then make the
> --
> 1.5.0.7
>
next prev parent reply other threads:[~2007-05-10 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 21:53 [PATCH] user-manual: Use "git config --global" instead of editing ~/.gitconfig Johan Herland
2007-05-10 22:02 ` J. Bruce Fields [this message]
2007-05-10 22:16 ` Johan Herland
2007-05-10 23:00 ` Petr Baudis
2007-05-11 3:46 ` J. Bruce Fields
2007-05-11 4:48 ` Junio C Hamano
2007-05-11 13:22 ` Nicolas Pitre
2007-05-11 20:23 ` Jan Hudec
2007-05-10 22:04 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070510220253.GZ13719@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.