git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wincent Colaiuta <win@wincent.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH 8/8] user-manual: simplify the user configuration
Date: Mon, 23 Mar 2009 01:07:03 +0100	[thread overview]
Message-ID: <984D312E-12B8-4A8C-B567-EF5AF1DDD3D6@wincent.com> (raw)
In-Reply-To: <94a0d4530903221601hb3bf8aelf98b22ee560dfb7b@mail.gmail.com>


El 23/3/2009, a las 0:01, Felipe Contreras escribió:

> On Mon, Mar 23, 2009 at 12:42 AM, Wincent Colaiuta <win@wincent.com>  
> wrote:
>> El 22/3/2009, a las 19:05, Felipe Contreras escribió:
>>
>>> 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.
>>>
>>> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
>>> ---
>>> Documentation/user-manual.txt |    8 +++-----
>>> 1 files changed, 3 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/Documentation/user-manual.txt b/Documentation/user- 
>>> manual.txt
>>> index b7678aa..c6ed940 100644
>>> --- a/Documentation/user-manual.txt
>>> +++ b/Documentation/user-manual.txt
>>> @@ -1015,13 +1015,11 @@ Telling git your name
>>> ---------------------
>>>
>>> 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:
>>> +easiest way is to use the linkgit:git-config[1] command:
>>>
>>> ------------------------------------------------
>>> -[user]
>>> -       name = Your Name Comes Here
>>> -       email = you@yourdomain.example.com
>>> +$ git config --global user.name "Your Name Comes Here"
>>> +$ git config --global user.email you@yourdomain.example.com
>>> ------------------------------------------------
>>>
>>> (See the '"CONFIGURATION FILE"' section of linkgit:git-config[1] for
>>> --
>>> 1.6.2.1.352.gae594
>>
>> See this lengthy thread:
>>
>> http://article.gmane.org/gmane.comp.version-control.git/106634
>
> I've obviously seen that thread because I started it.

Yeah, I noticed that only after sending my message. I hadn't realised  
at first because the patch really looked like it was written by  
someone who hadn't ever seen the thread, as it doesn't address the  
points raised in the thread at all.

> Can you write more than one line to explain your point?

I was thinking mostly of Junio's comments:

http://article.gmane.org/gmane.comp.version-control.git/106667

'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. I actually  
wish this section appeared a lot earlier in the document, but
that is a separate issue.'

If you expect him to apply your patch, you'll probably want to address  
those concerns (and possibly others raised in referenced thread) in  
the commit message.

Cheers,
Wincent

  parent reply	other threads:[~2009-03-23  0:08 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22 18:05 [RFC/PATCH 0/8] user-manual: style improvements Felipe Contreras
2009-03-22 18:05 ` [RFC/PATCH 1/8] user-manual: remove some git-foo usage Felipe Contreras
2009-03-22 18:05   ` [RFC/PATCH 2/8] docbook: improve css style Felipe Contreras
2009-03-22 18:05     ` [RFC/PATCH 3/8] docbook: radical style change Felipe Contreras
     [not found]       ` <1237745121-6325-5-git-send-email-felipe.contreras@gmail.com>
2009-03-22 18:05         ` [RFC/PATCH 5/8] user-manual: use 'fast-forward' instead of 'fast forward' Felipe Contreras
2009-03-22 18:05           ` [RFC/PATCH 6/8] user-manual: use SHA-1 instead of SHA1 or sha1 Felipe Contreras
2009-03-22 18:05             ` [RFC/PATCH 7/8] user-manual: add global config section Felipe Contreras
2009-03-22 18:05               ` [RFC/PATCH 8/8] user-manual: simplify the user configuration Felipe Contreras
2009-03-22 22:42                 ` Wincent Colaiuta
2009-03-22 23:01                   ` Felipe Contreras
2009-03-23  0:00                     ` Junio C Hamano
2009-03-23 11:02                       ` Felipe Contreras
2009-03-23  0:07                     ` Wincent Colaiuta [this message]
2009-03-23 11:07                       ` Felipe Contreras
2009-03-23 11:09                         ` Wincent Colaiuta
2009-03-24  0:22                           ` Felipe Contreras
2009-03-24 21:52               ` [RFC/PATCH 7/8] user-manual: add global config section J. Bruce Fields
2009-03-24 22:17                 ` Felipe Contreras
2009-03-24 22:42                   ` J. Bruce Fields
2009-03-23  6:50       ` [RFC/PATCH 3/8] docbook: radical style change Jeff King
2009-03-23 10:47         ` Felipe Contreras
2009-03-23  6:42     ` [RFC/PATCH 2/8] docbook: improve css style Jeff King
2009-03-23 10:31       ` Felipe Contreras
2009-03-23 15:20         ` Michael J Gruber
2009-03-24  0:21           ` Felipe Contreras
2009-03-24  2:08             ` Junio C Hamano
2009-03-24  7:52               ` Felipe Contreras
2009-03-24  8:18                 ` Jeff King
2009-03-24  8:57                   ` Felipe Contreras
2009-03-24  9:00                     ` Jeff King
2009-03-24  9:39                       ` Felipe Contreras
2009-03-24  8:29             ` Michael J Gruber
2009-03-24  9:06               ` Felipe Contreras
2009-03-24  9:16                 ` Jeff King
2009-03-24 10:39                 ` Michael J Gruber
2009-03-24 10:52                   ` Felipe Contreras
2009-03-24  0:20       ` Felipe Contreras
2009-03-24  8:42         ` Jeff King
2009-03-23  6:31   ` [RFC/PATCH 1/8] user-manual: remove some git-foo usage Jeff King
2009-03-23 10:54     ` Felipe Contreras

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=984D312E-12B8-4A8C-B567-EF5AF1DDD3D6@wincent.com \
    --to=win@wincent.com \
    --cc=felipe.contreras@gmail.com \
    --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).