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

git-format-patch-script bug?

From
Eric W. Biederman <ebiederm@xmission.com>
Date
Aug 7, 2005, 07:35 UTC
Message-ID
<m1d5oqxkqm.fsf@ebiederm.dsl.xmission.com>

I haven't had a chance to investigate this much yet but I have ran into a peculiar problem.

I was trying to help someone track down a bug that occurred between linux-2.6.12 and linux-2.6.13-rc1. Since it was very much an unknown where the problem was introduced I decided to run git format-patch so I could see what all of the differences were. Then to be certain the patch series worked I started applying them in order. 

I didn't get very far when I had a patch conflict.

Looking deeper git-diff-tree is always making the diffs against the parent instead of against the next commit in the series. Which is largely sane. However it does not warn or fail when the parents and the next commit are different, which seems nonintuitive.

Eric
Next: Junio C Hamano
Message 1 of 4 in “git-format-patch-script bug?”
  1. Eric W. BiedermanAug 7, 2005
  2. Junio C HamanoAug 7, 2005
  3. Eric W. BiedermanAug 7, 2005
  4. Junio C HamanoAug 7, 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.