Re: [RFC/PATCH 8/8] user-manual: simplify the user configuration

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Mar 23, 2009, 11:02 UTC
Message-ID: <94a0d4530903230402y402daf8fw822f87feb6e9fd8c@mail.gmail.com>
In-Reply-To: <7viqm1az1k.fsf@gitster.siamese.dyndns.org>

On Mon, Mar 23, 2009 at 2:00 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 20 quoted lines

> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>>> See this lengthy thread:
>>>
>>> http://article.gmane.org/gmane.comp.version-control.git/106634
>>
>> I've obviously seen that thread because I started it.
>>
>> Can you write more than one line to explain your point?
>
> The "lengthy thread" look lengthier than necessary because it has a
> more-or-less unrelated side topic ("where is $HOME on Windows"), but I
> think the main point by WIncent is that onus lies on whoever repeats the
> previous discussion to provide what is different in this round to convince
> others to read the patch.  For example, this
>
>    http://article.gmane.org/gmane.comp.version-control.git/106657
>
> was not answered by you in the previous round, and I do not think this
> round is any different.

Was I supposed to answer it? I am trying to address the points raised in those discussions in this patch series.

Show 7 quoted lines

> I personally find that between what Wincent presented in
>
>    http://article.gmane.org/gmane.comp.version-control.git/106673
>
> as "Something like either ... or ...", the first one that shows the actual
> configuration file contents and then mention 'git config' a good enough
> compromise.

Except that in the previous patch[1] (#7) I'm adding a new global section that explains how to configure git in different ways:

I don't think it makes sense to explain "either ... or ..." each time we deal with 'git config' in the manual if it's explained in the very beginning.

[1] http://article.gmane.org/gmane.comp.version-control.git/114163

-- 
Felipe Contreras