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

Re: Per-file, possibly even per-hunk cherry picking

From
Sam Vilain <sam@vilain.net>
Date
Jul 10, 2007, 12:48 UTC
Message-ID
<4693800F.4010308@vilain.net>
In-Reply-To
<469378AB.7030909@vilain.net>
Sam Vilain wrote:
Show 5 quoted lines
> I'm interested in extending the cherry analysis to allow specification
> of the diff options used when calculating diff IDs, presenting the
> calculated diff IDs for analysis by external tools, and even calculating
> and dealing with per-hunk diff IDs.
>   

On reflection I think so long as --cherry-pick works together with a file selection, it would probably be enough.

ie, if I have these commits:
A---B
 \
  \
   C

B changes a file foo.c, adding a line of text. C changes foo.c as well as bar.c, but the change in foo.c was identical to change B.

I want this to show me nothing:
  git-rev-list --left-right --cherry-pick B...C -- foo.c

Would it be the right approach to put this information in ids->diffopts, or somewhere else?

Sam.
Previous: Sam VilainNext: Johannes Schindelin
Message 2 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.