From: Johan Herland <johan@herland.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] user-manual: Use "git config --global" instead of editing ~/.gitconfig
Date: Fri, 11 May 2007 00:16:18 +0200 [thread overview]
Message-ID: <200705110016.18319.johan@herland.net> (raw)
In-Reply-To: <20070510220253.GZ13719@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Friday 11 May 2007, J. Bruce Fields wrote:
> 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.
I see your point, but when I look at the user manual, the only place I can
actually find git-config used is in [[remote-branch-configuration]].
Besides, we also present the config-file syntax for user.{name,email} in
[[telling-git-your-name]], so it's not like I'm remove every reference to
the layout of .gitconfig.
Maybe we can present both versions in [[making-changes]]?
Have fun!
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2007-05-10 22:17 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
2007-05-10 22:16 ` Johan Herland [this message]
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=200705110016.18319.johan@herland.net \
--to=johan@herland.net \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).