From: Simon Marchi <simon.marchi@polymtl.ca>
To: Christian Biesinger <cbiesinger@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>, binutils@sourceware.org
Subject: Re: [PATCH] Import mklog.py from gcc repo
Date: Fri, 18 Sep 2020 10:50:41 -0400 [thread overview]
Message-ID: <ba007054-b247-f0e4-ff46-8f6d138d5a52@polymtl.ca> (raw)
In-Reply-To: <CAPTJ0XGj5pAe2mxkNKU4d+JpOwK6AUcRTSYO+X+HawwarBy9rA@mail.gmail.com>
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
next prev parent reply other threads:[~2020-09-18 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 20:29 Simon Marchi
2020-09-18 14:27 ` Christian Biesinger
2020-09-18 14:48 ` Alex Coplan
2020-09-18 14:50 ` Simon Marchi [this message]
2020-09-21 12:45 ` Martin Liška
2020-09-21 14:33 ` Simon Marchi
2020-09-21 15:31 ` Simon Marchi
2020-09-25 14:25 ` Simon Marchi
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=ba007054-b247-f0e4-ff46-8f6d138d5a52@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=binutils@sourceware.org \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).