From: Wincent Colaiuta <win@wincent.com>
Date: Sat, 22 Mar 2008 15:41:35 GMT
Subject: Re: [PATCH] git add --interactive: Autoselect single patch file
Message-ID: <6AA0A7C2-488B-4440-A797-B1B87361801D@wincent.com>
In-Reply-To: <alpine.LSU.1.00.0803221549570.4124@racer.site>

El 22/3/2008, a las 15:51, Johannes Schindelin escribió:

> Hi,
>
> On Sat, 22 Mar 2008, Jörg Sommer wrote:
>
>> If there's only one file to patch, select it automaticly and don't
>> bother the user. In the case he didn't want do patching, he can say  
>> 'd'
>> at the patch prompt.
>
> It also triggers when you specified a single path:
>
> 	$ git add -i that-file.c
>
> I like it.
>
> However, if I already specify (a) file(s), could add -i not go to the
> [p]atch option right away?

That's what I originally wanted and I sent a couple of patches in to  
that effect some months back. But it was argued that it is useful for  
passed-in filepatterns to limit the scope of other operations in "git  
add -i", not just the [p] subcommand, and that in turn lead to the "-- 
patch" option being implemented. I can try to dig up the message-ids  
in question if you are interested.

Still, I use the [p] subcommand so often (and almost never use any of  
the other subcommands offered by "git add -i") that I have "git patch"  
set up as an alias for "git add --patch".

Cheers,
Wincent