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

git-format-patch possible regressions

From
MCMarco Costalba <mcostalba@gmail.com>
Date
May 25, 2006, 19:23 UTC
Message-ID
<e5bfff550605251223g2cf8cfb9vfa18d016b369188d@mail.gmail.com>
A couple of possible regressions:
1) Unreconized --signoff option

$ git --version git version 1.3.3.ged90 $ git-format-patch -s HEAD^..HEAD 0001-cat-file-document-p-option.txt $ git-format-patch --signoff HEAD^..HEAD fatal: unrecognized argument: --signoff

2) Unhandled ranges list

$ git --version git version 1.3.3.ged90 $ git-format-patch -s HEAD^..HEAD HEAD^^..HEAD^ 0001-cat-file-document-p-option.txt

$ git --version git version 1.3.3.gf205 git checkout -b test 51ce34b9923d9b119ac53414584f80e05520abea $ git-format-patch HEAD^..HEAD HEAD^^..HEAD^ 0001-Builtin-git-show-branch.txt 0002-Builtin-git-apply.txt

Both regressions brake qgit. The first one is easy to fix (--signoff --> -s) The second one is not so easy. It is use to format a patch series starting from a mouse selected multiple revisions. Note that the revisions could be not consecutive. Note also that looping git-format-patch for each revision does not updates patch number that always stay at 0001.

Feeding all the selected revisions in one go in the form git-format-patch sel1^..sel1 sel2^..sel2 ........ seln^..seln is the only way I have found to:

1) create a patch series of (randomly) selected revisions
2) increment patch numbers for each patch
   Marco
Next: Linus Torvalds
Message 1 of 14 in “git-format-patch possible regressions”
  1. Marco CostalbaMay 25, 2006
  2. Linus TorvaldsMay 25, 2006
  3. Marco CostalbaMay 25, 2006
  4. Junio C HamanoMay 25, 2006
  5. Marco CostalbaMay 25, 2006
  6. Johannes SchindelinMay 25, 2006
  7. Johannes SchindelinMay 25, 2006
  8. Junio C HamanoMay 25, 2006
  9. Johannes SchindelinMay 25, 2006
  10. Marco CostalbaMay 26, 2006
  11. Junio C HamanoMay 26, 2006
  12. Jakub NarebskiMay 26, 2006
  13. Marco CostalbaMay 27, 2006
  14. Johannes SchindelinMay 28, 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.