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

git-format-patch builtin isn't using git-cherry?

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jun 23, 2006, 00:32 UTC
Message-ID
<46a038f90606221732k6d93bcceic2761081d7a7c72b@mail.gmail.com>

I used to rely on git-format-patch to be calling git-cherry in the bg, so that I'd know that the obviously merged patches were upstream alredy. It doesn't seem to do it any more.

Reading cmd_format_patch() in builtin-log.c, it seems to have lost that magic that made it so useful... :( Can a kind soul that speaks C fluently help me out here?

(The new format-patch gives me 180 patches to merge/rebase, where the old one tells me there's only 51. guess which one I prefer ;-) )

cheers,
m
Next: Johannes Schindelin
Message 1 of 5 in “git-format-patch builtin isn't using git-cherry?”
  1. Martin LanghoffJun 23, 2006
  2. Johannes SchindelinJun 23, 2006
  3. Timo HirvonenJun 23, 2006
  4. Johannes SchindelinJun 23, 2006
  5. diff: add diff_flush_patch_id()Johannes Schindelin, Jun 23, 2006

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.