This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Cherry Picking git Patches and ChangeLog
- From: Andreas Schwab <schwab at linux-m68k dot org>
- To: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- Cc: "gdb\ at sourceware dot org" <gdb at sourceware dot org>, Chris Johns <chrisj at rtems dot org>
- Date: Mon, 16 Mar 2015 00:03:18 +0100
- Subject: Re: Cherry Picking git Patches and ChangeLog
- Authentication-results: sourceware.org; auth=none
- References: <550609D6 dot 2020003 at oarcorp dot com> <874mplvq2i dot fsf at igel dot home> <F9484EDF-26AF-478A-B61E-40FBC1A27CCC at oarcorp dot com>
Joel Sherrill <joel.sherrill@oarcorp.com> writes:
> On March 15, 2015 5:44:21 PM CDT, Andreas Schwab <schwab@linux-m68k.org> wrote:
>>Joel Sherrill <joel.sherrill@oarcorp.com> writes:
>>
>>> I know that this is really a git/ChangeLog/patch question but
>>> since it comes up in context of gdb, I am asking here. How
>>> does one deal with patches that would apply cleanly except
>>> for ChangeLog?
>>
>>git-merge-changelog can help here.
>
> That will help if we want to manually touch the patches and update them for the tarball.
Please explain what you are trying to do. Cherry picking will use the
configured merge driver.
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."