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

[RFE/RFC] format-patch/diff via path

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Jan 20, 2018, 06:26 UTC
Message-ID
<018601d391b7$8e8686a0$ab9393e0$@nexbridge.com>
I’m still a bit perplexed by some behaviour seen today, and am looking for a clean way to deal with it that the documentation does not make clear. So, I’m asking in a different way. Suppose a graph of
A---B---C---D---E
\      \               /
  \----F—G----/
When trying to perform a format-patch from B to E, I was seeing commits B-A-F-G-E rather than what I wanted B-C-D-E.  F and G were younger commits than C and D, which I assume (very likely wrongly) is why diff was giving preferential treatment to that path.
What I am trying to figure out is whether there is a clean way to force format-patch along the B-C-D-E path. If not, would it be worth starting up a small project to make this possible (not knowing exactly where to start), but I would envision something like: git format-patch –via=C B..E
I may be just missing something obvious (new to format-patch operations myself). 

Cheers, Randall P.S. Bad ideas happen when tests run for a long time 😉

-- Brief whoami:
  NonStop developer since approximately NonStop(211288444200000000)
  UNIX developer since approximately 421664400
-- In my real life, I talk too much.
Next: Junio C Hamano
Message 1 of 3 in “[RFE/RFC] format-patch/diff via path”
  1. Randall S. BeckerJan 20, 2018
  2. Junio C HamanoJan 20, 2018
  3. Randall S. BeckerJan 20, 2018

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.