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

Re: git-rev-list and git-format-patch script oddness

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Sep 11, 2005, 09:20 UTC
Message-ID
<Pine.LNX.4.63.0509111120020.32244@wgmdd8.biozentrum.uni-wuerzburg.de>
In-Reply-To
<46a038f905091101529e045af@mail.gmail.com>
Hi,
On Sun, 11 Sep 2005, Martin Langhoff wrote:
Show 6 quoted lines
> When I run git-format-patch, it insists on outputting merges that have
> already been merged upstream, regardless of the fact that
> git-merge-base knows better.
> 
> Is there a way to get it to skip merged-in patches that git already
> has detected as merged upstream?
I always use something like
	git-format-patch HEAD ^origin

Hth, Dscho

Previous: Martin LanghoffNext: Junio C Hamano
Message 2 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.