Re: [kernel.org users] [RFD] On deprecating "git-foo" for builtins

[Perry Wagle <wagle@cs.indiana.edu>]

On Aug 28, 2008, at 12:52 PM, Teemu Likonen wrote:

> Perry Wagle wrote (2008-08-28 12:24 -0700):
>
>> Is is really only that I
>>
>>    sed s/git-/git<SPACE>/g
>>
>> on the scripts?  I'm doubting it, given the quality of reasoning and
>> lack of respect for upward compatibility on this thread.
>
> I have come to understand that "git " has quite long time been more
> robust and portable way of writing scripts. They work in both
> configurations so I'd definitely suggest doing "s/git-/git /g" for  
> every
> script. Of course in an interactive shell everyone can use whatever  
> they
> prefer and works at the moment.

Sure.  Its an extra fork in git command intensive scripts (and git is  
racey still maybe), but *shrug*.

When I started with git in Fall 2007, the sample scripts and gitweb  
both used git<DASH> and git<SPACE> willy-nilly.  I liked git<DASH>  
better since it was what I used at the command line for the <TAB>  
completion for the commands and for the man pages, and I like being  
meticulously consistent so I can greatly reduce mistakes.

Even as of March 2008 (our last sync with git before the git scripting  
was completed and we got on to other things), the sample scripts and  
gitweb still used the git<DASH> form.  If this has been brewing for  
two years, there shouldn't have been a git<DASH> form in the scripts  
in the standard source *anywhere* for those two years.

There was.  Therefore, you don't get to claim that this was decided  
two years ago, finally done now, and what's Perry's problem anyway?

But, my problem is not git<DASH> vs git<SPACE>, but the slap-dash way  
upward compatibility was broken and the "water over the dam" slippery  
slope rationalizations that refuse to consider reverting.  "You" will  
do it again in the future since you are declaring success here.  And  
"you" have likely done it in the past 6 months.

-- Perry