[PATCH] Teach mklog to reference PRs.

[Martin Liška]

On 8/2/19 8:04 AM, Martin Liška wrote:
> On 8/2/19 7:45 AM, Martin Liška wrote:
>> I agree with that approach.
> 
> I'm sending an example how it would look like for something
> bigger:
> 
> $ git diff e8a3be407068bfb9c82f0f6656b30d26cc2f484a~15..e8a3be407068bfb9c82f0f6656b30d26cc2f484a > patch && ./contrib/mklog patch > changelog.txt
> 
> Thoughts?
> 
> Martin
> 

Hello.

I've reconsidered the ChangeLog format and I would like to "revert" my decision.
I prefer to stay with the current format because:

1) each changelog entry can directly be copied to a ChangeLog file;
   no need for appending PRxxx and authors from the changelog
2) I have a working script that applies such patches to SVN:
   https://github.com/marxin/gcc-util/blob/master/boilerplate/applypatch.py

  If there's an interest, I can clean it up and suggest to contrib

3) I also have a script that extracts patch and changelog entries back
   to email message:
   https://github.com/marxin/script-misc/blob/master/gcc-extract-backport-patches.py

  That's handy for backporting where one wants to not have a ChangeLog collisions.
  Then I use applypatch.py --backport to apply extracted changes with 'Backport from mainline'
  header.

What others do for patch application and back extracting for backport testing?
I'm sending an example of patch backport for 2a245bc81b9e09cba4930d12d0417da229c37d67.

Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-patch-273660.patch
Type: text/x-patch
Size: 3019 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/gcc-patches/attachments/20190812/9d67a517/attachment.bin>