[PATCH] Import mklog.py from gcc repo

Simon Marchi simon.marchi@polymtl.ca
Fri Sep 18 14:50:41 GMT 2020


On 2020-09-18 10:27 a.m., Christian Biesinger wrote:
> I like this in principle, but the one annoying part is that no longer
> prints the patch author/date line, so you have to manually create it.
> I suppose one could make their own script for that (or maybe emacs
> users have a macro for that or something)...

I think you could add an option to the script to do this, I don't see
why they would reject that.  I don't know what the workflow of the gcc
devs is regarding this.

But it's not a problem from my point of view.  I prefer to write my
ChangeLog entries in the commit message without the header.  I think
it's pointless to put a date there, because the final date will be the
date where I actually push the patch on the upstream master branch.  And
the name/email is redundant with the author name/email of the commit.

I use a script [1] to insert the entries in the ChangeLog files and
amend the commit when I'm about to push to upstream master.  The script
automatically generates the date/name/email line at that moment.

Simon

[1] https://github.com/simark/gnu-changelog-tools/blob/master/changelog-git-amend/changelog-git-amend.py


More information about the Gdb-patches mailing list