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

Re: git format-patch --break-rewrites broken in 2.9.3

From
Philip Oakley <philipoakley@iee.org>
Date
Aug 19, 2016, 18:04 UTC
Message-ID
<04D3C5DBA44C4AC48D0D846B337D2EE0@PhilipOakley>
In-Reply-To
<20160818144421.GA9062@aepfle.de>
On Thu, Aug 18, 2016 at 04:44:21PM +0200, Olaf Hering wrote:
Show 13 quoted lines
> This command used to create a diff which can be consumed by patch. But
> at least with 2.9.3 it just gives a rename output:
>
>  git format-patch \
>         --no-signature \
>         --stdout \
>         --break-rewrites \
>         --keep-subject \
> 
> 95fa0405c5991726e06c08ffcd8ff872f7fb4f2d^..95fa0405c5991726e06c08ffcd8ff872f7fb4f2d
>
>
> What must be done now to get a usable patch?
As an aside, the range can be shortened to
95fa0405c5991726e06c08ffcd8ff872f7fb4f2d^!

It's something I picked up when doing the doc update on 'specifying revisions'.

--
Philip
Previous: Jeff KingNext: Andreas Schwab
Message 7 of 11 in “git format-patch --break-rewrites broken in 2.9.3”
  1. Olaf HeringAug 18, 2016
  2. Johannes SchindelinAug 18, 2016
  3. Junio C HamanoAug 18, 2016
  4. Junio C HamanoAug 18, 2016
  5. Jeff KingAug 18, 2016
  6. Jeff KingAug 18, 2016
  7. Philip OakleyAug 19, 2016
  8. Andreas SchwabAug 19, 2016
  9. Jeff KingAug 18, 2016
  10. Olaf HeringAug 18, 2016
  11. Matthieu MoyAug 18, 2016

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.