git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Wincent Colaiuta <win@wincent.com>
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 17:00:44 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.1.00.0803221700220.4353@racer.site> (raw)
In-Reply-To: <6AA0A7C2-488B-4440-A797-B1B87361801D@wincent.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 863 bytes --]

Hi,

On Sat, 22 Mar 2008, Wincent Colaiuta wrote:

> El 22/3/2008, a las 15:51, Johannes Schindelin escribió:
> 
> >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".

Ah, I missed the --patch option.

Thanks,
Dscho

  reply	other threads:[~2008-03-22 16:01 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
2008-03-22 16:00     ` Johannes Schindelin [this message]
  -- 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=alpine.LSU.1.00.0803221700220.4353@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=joerg@alea.gnuu.de \
    --cc=normalperson@yhbt.net \
    --cc=win@wincent.com \
    /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).