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

Re: [PATCH 3/2] format-patch: use clear_commit_marks() instead of some adhocery

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jun 26, 2006, 22:20 UTC
Message-ID
<46a038f90606261520k7df8cb3ci7a4a609644e0be12@mail.gmail.com>
In-Reply-To
<Pine.LNX.4.63.0606261728340.29667@wbgn013.biozentrum.uni-wuerzburg.de>

git-format-patch is rather broken on pu right now (pre these patches). In my test git repo, git-format-patch.sh called with 2 parameters, like

  git-format-patch <remotehead> <myhead>

when HEAD != myhead does the right thing, but git format-patch doesn't, it seems to be messing up and not finding the merge base correctly:

  0001-Initial-revision-of-git-the-information-manager-from-hell.txt
And it errors out with ignore-if-in-upstream:
  $ ./git format-patch --ignore-if-in-upstream -o .patches origin master
  fatal: Not a range.
I'll retest later with these patches and post again.
martin
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 5 of 20 in “resurrect format-patch's patch id checking”
  1. 0/2 resurrect format-patch's patch id checkingJohannes Schindelin, Jun 25, 2006
  2. 3/2 format-patch: use clear_commit_marks() instead of some adhoceryJohannes Schindelin, Jun 26, 2006
  3. Junio C HamanoJun 26, 2006
  4. Johannes SchindelinJun 26, 2006
  5. Martin LanghoffJun 26, 2006
  6. Johannes SchindelinJun 26, 2006
  7. Martin LanghoffJun 26, 2006
  8. Johannes SchindelinJun 26, 2006
  9. Junio C HamanoJun 26, 2006
  10. format-patch: support really old non-range syntax, with a warningJohannes Schindelin, Jun 26, 2006
  11. Martin Langhoff (CatalystIT)Jun 26, 2006
  12. Johannes SchindelinJun 26, 2006
  13. Johannes SchindelinJun 27, 2006
  14. Martin LanghoffJun 27, 2006
  15. Johannes SchindelinJun 27, 2006
  16. Martin LanghoffJun 27, 2006
  17. Johannes SchindelinJun 27, 2006
  18. Junio C HamanoJun 26, 2006
  19. Johannes SchindelinJun 26, 2006
  20. format-patch: use clear_commit_marks() instead of some adhoceryJohannes Schindelin, Jun 27, 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.