Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)

[Junio C Hamano <gitster@pobox.com>]

Michael J Gruber <git@drmicha.warpmail.net> writes:

> Junio C Hamano venit, vidit, dixit 05.12.2010 07:30:
> ...
>> 
>> * mg/cvsimport (2010-11-28) 3 commits
>>  - cvsimport.txt: document the mapping between config and options
>>  - cvsimport: fix the parsing of uppercase config options
>>  - cvsimport: partial whitespace cleanup
>> 
>> I was being lazy and said "Ok" to "cvsimport.capital-r" but luckily other
>> people injected sanity to the discussion.  Weatherbaloon patch sent, but
>
> I assume I should try and not read too much into this...

No, you shouldn't.  I wasn't questioning _your_ sanity, and if you took it
that way, I apologize.

I as the maintainer have different priority from contributors.  The
contributed patches want to "get the job done" first, and their solution
only need to be "correct and not too ugly".

I however in addition need to make sure that the changes make sense in the
longer term, and my saying "Ok" to "capital-r" instead of rejecting the
patch totally went against that obligation of mine.  I'll have a hard time
justifying why users need to type that long string that does not convey
much information in three months.  It was _my_ temporary insanity that
came from fatigue.

So an weatherbaloon patch was sent as a counterproposal, which I think it
shows the best course of action given the existing constraints, but there
may be better ones.  If you agree, and if you have time and inclination, a
reroll in that direction would be appreciated.  And it does not have to be
you but others on the list.