git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Fix --cherry-pick with given paths

From
Sam Vilain <sam@vilain.net>
Date
Jul 10, 2007, 14:22 UTC
Message-ID
<4693960C.1010906@vilain.net>
In-Reply-To
<Pine.LNX.4.64.0707101449220.4047@racer.site>
Johannes Schindelin wrote:
Show 11 quoted lines
> 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.
Previous: Johannes SchindelinNext: Junio C Hamano
Message 4 of 5 in “Per-file, possibly even per-hunk cherry picking”
  1. Sam VilainJul 10, 2007
  2. Sam VilainJul 10, 2007
  3. Fix --cherry-pick with given pathsJohannes Schindelin, Jul 10, 2007
  4. Sam VilainJul 10, 2007
  5. Junio C HamanoJul 11, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.