From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] user-manual: Simplify the user configuration.
Date: Wed, 21 Jan 2009 21:39:27 +0200 [thread overview]
Message-ID: <94a0d4530901211139x6296a48m14aa7ce1d8e65145@mail.gmail.com> (raw)
In-Reply-To: <20090121191808.GF21686@coredump.intra.peff.net>
On Wed, Jan 21, 2009 at 9:18 PM, Jeff King <peff@peff.net> wrote:
> On Wed, Jan 21, 2009 at 09:04:10PM +0200, Felipe Contreras wrote:
>
>> 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 seem to recall this coming up several times before, and there being a
> sentiment that it was _good_ to introduce the user to concept of a
> config file. It lets them know that it exists, approximately what the
> syntax looks like, and demystifies what is going on when you type "git
> config" (i.e., it intentionally shows that there is more than way to do
> it).
>
> I don't have a personal preference, but you may want to grep the
> list archives for other discussion.
That's over complicating the user with what should probably be one of
the first things to do. Besides, do Windows users know which is their
home directory?
Maybe a comment like previous git config commands:
If you examine the file .gitconfig in your home directory, you will see this:
------------------------------------------------
...
[user]
name = Your Name Comes Here
email = you@yourdomain.example.com
...
------------------------------------------------
--
Felipe Contreras
next prev parent reply other threads:[~2009-01-21 19:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:09 [PATCH 1/2] user-manual: Simplify the user configuration Felipe Contreras
2009-01-21 18:09 ` [PATCH 2/2] Fix typo Felipe Contreras
2009-01-21 18:55 ` [PATCH 1/2] user-manual: Simplify the user configuration Markus Heidelberg
2009-01-21 19:04 ` [PATCH] " Felipe Contreras
2009-01-21 19:18 ` Jeff King
2009-01-21 19:39 ` Felipe Contreras [this message]
2009-01-21 19:51 ` Jeff King
2009-01-21 20:54 ` [PATCH 1/2] " Junio C Hamano
2009-01-21 21:13 ` Wincent Colaiuta
2009-01-21 21:19 ` Felipe Contreras
2009-01-22 16:17 ` Hannu Koivisto
2009-01-22 16:57 ` Felipe Contreras
2009-01-22 17:14 ` Junio C Hamano
2009-01-22 17:28 ` Johannes Schindelin
2009-01-22 18:59 ` Hannu Koivisto
2009-01-24 8:21 ` Felipe Contreras
2009-01-24 13:42 ` Johannes Schindelin
2009-01-24 14:04 ` Felipe Contreras
2009-01-25 20:34 ` Junio C Hamano
2009-01-25 21:12 ` Felipe Contreras
2009-01-25 21:44 ` Jeff King
2009-01-25 22:55 ` Wincent Colaiuta
2009-01-25 23:20 ` Jeff King
2009-01-25 7:32 ` Kyle Moffett
2009-01-25 12:06 ` Johannes Schindelin
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=94a0d4530901211139x6296a48m14aa7ce1d8e65145@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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 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).