From: Sam Vilain <sam@vilain.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix --cherry-pick with given paths
Date: Wed, 11 Jul 2007 02:22:04 +1200 [thread overview]
Message-ID: <4693960C.1010906@vilain.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707101449220.4047@racer.site>
Johannes Schindelin wrote:
> If you say --cherry-pick, you do not want to see patches which are
> in the upstream. If you specify paths with that, what you usually
> expect is that only those parts of the patches are looked at which
> actually touch the given paths.
>
> With this patch, that expectation is met.
>
> Noticed by Sam Vilain.
>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
>
I just tested this, and it seems to work just like I hoped, so:
Signed-off-by: Sam Vilain <sam.vilain@catalyst.net.nz>
Sam.
next prev parent reply other threads:[~2007-07-10 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 12:16 Per-file, possibly even per-hunk cherry picking Sam Vilain
2007-07-10 12:48 ` Sam Vilain
2007-07-10 13:50 ` [PATCH] Fix --cherry-pick with given paths Johannes Schindelin
2007-07-10 14:22 ` Sam Vilain [this message]
2007-07-11 22:00 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4693960C.1010906@vilain.net \
--to=sam@vilain.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).