From: Andreas Schwab <schwab@linux-m68k.org>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: "Olaf Hering" <olaf@aepfle.de>, <git@vger.kernel.org>
Subject: Re: git format-patch --break-rewrites broken in 2.9.3
Date: Fri, 19 Aug 2016 20:41:37 +0200 [thread overview]
Message-ID: <87inuwiota.fsf@linux-m68k.org> (raw)
In-Reply-To: <04D3C5DBA44C4AC48D0D846B337D2EE0@PhilipOakley> (Philip Oakley's message of "Fri, 19 Aug 2016 19:04:50 +0100")
On Aug 19 2016, "Philip Oakley" <philipoakley@iee.org> wrote:
> On Thu, Aug 18, 2016 at 04:44:21PM +0200, Olaf Hering wrote:
>
>> 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^!
In the context of format-patch you can also use -1 to select the topmost
commit from the list.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2016-08-19 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 14:44 git format-patch --break-rewrites broken in 2.9.3 Olaf Hering
2016-08-18 15:05 ` Jeff King
2016-08-18 15:15 ` Jeff King
[not found] ` <vpqa8gayumw.fsf@anie.imag.fr>
2016-08-18 15:40 ` Jeff King
2016-08-18 15:48 ` Olaf Hering
2016-08-18 16:16 ` Matthieu Moy
2016-08-18 15:15 ` Johannes Schindelin
2016-08-18 17:27 ` Junio C Hamano
2016-08-18 20:42 ` Junio C Hamano
2016-08-19 18:04 ` Philip Oakley
2016-08-19 18:41 ` Andreas Schwab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87inuwiota.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=philipoakley@iee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.