From: Wincent Colaiuta <win@wincent.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Jörg Sommer" <joerg@alea.gnuu.de>,
git@vger.kernel.org, normalperson@yhbt.net
Subject: Re: [PATCH] git add --interactive: Autoselect single patch file
Date: Sat, 22 Mar 2008 16:41:35 +0100 [thread overview]
Message-ID: <6AA0A7C2-488B-4440-A797-B1B87361801D@wincent.com> (raw)
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
next prev parent reply other threads:[~2008-03-22 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 1:22 [PATCH] git add --interactive: Autoselect single patch file Jörg Sommer
2008-03-22 14:51 ` Johannes Schindelin
2008-03-22 15:41 ` Wincent Colaiuta [this message]
2008-03-22 16:00 ` Johannes Schindelin
-- strict thread matches above, loose matches on Subject: below --
2008-02-28 11:15 Jörg Sommer
2008-02-29 2:00 ` Xavier Maillard
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6AA0A7C2-488B-4440-A797-B1B87361801D@wincent.com \
--to=win@wincent.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=joerg@alea.gnuu.de \
--cc=normalperson@yhbt.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).