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

Re: [PATCH] Omit patches that have already been merged from format-patch output.

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Sep 11, 2005, 21:08 UTC
Message-ID
<46a038f90509111408f9479e2@mail.gmail.com>
In-Reply-To
<7voe6zqr9y.fsf@assigned-by-dhcp.cox.net>
>  git-cherry).  One thing I am reluctant about this is it breaks the
>  exact example Johannes just posted.

Well, Johannes example didn't work at all for me. Output was empty, when I was expecting 4~6 entries.

cheers,
martin
Previous: Junio C HamanoNext: Martin Langhoff
Message 4 of 9 in “git-rev-list and git-format-patch script oddness”
  1. Martin LanghoffSep 11, 2005
  2. Johannes SchindelinSep 11, 2005
  3. Omit patches that have already been merged from format-patch output.Junio C Hamano, Sep 11, 2005
  4. Martin LanghoffSep 11, 2005
  5. Martin LanghoffSep 11, 2005
  6. Martin LanghoffSep 12, 2005
  7. Martin LanghoffSep 12, 2005
  8. Junio C HamanoSep 12, 2005
  9. Martin LanghoffSep 12, 2005

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.