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

Re: git format-patch can clobber existing patch

From
ΣΝΣταύρος Ντέντος <stdedos@gmail.com>
Date
Feb 21, 2019, 14:25 UTC
Message-ID
<CAHMHMxUfjnNXFikVD=rys_t5BUho=7uRw4LsXgAphFwSf3xOnw@mail.gmail.com>
In-Reply-To
<CAHMHMxVdpOnTkf9RHzCa+YjjvpqJApsSE03Jjyb_VbJp_4q-jw@mail.gmail.com>
Hello there,

During my work flow, I tend to use `git format-patch` to move patches around (nasty, I know, but bear with me)

It has occured to me that, it is possible that `git format-patch` can clobber existing files, if they match in the name and in the "patch order". However, if the patch is one, then, it will normally start with `0001-x.patch`

It was fine for me when I pushed updates of the same "patch series". Now that I wanted to diff a "previous patch file" with the patch upstream, however, it was almost a "disaster". :-)

Would it make sense / be easy enough to have some clobbering check / flag?
Ντέντος Σταύρος
Next: Junio C Hamano
Message 1 of 5 in “Re: git format-patch can clobber existing patch”
  1. Σταύρος ΝτέντοςFeb 21, 2019
  2. Junio C HamanoFeb 21, 2019
  3. brian m. carlsonFeb 22, 2019
  4. Junio C HamanoFeb 22, 2019
  5. Σταύρος ΝτέντοςFeb 23, 2019

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.