This is the mail archive of the
mailing list for the glibc project.
Re: Automating the maintenance of the ChangeLog file
On Tue, 27 Nov 2018, Zack Weinberg wrote:
On Tue, Nov 27, 2018 at 2:29 AM Florian Weimer <email@example.com> wrote:
* Zack Weinberg:
Specifically, I propose: Effective immediately, project policy
requires the Git commit message for each commit to end with the full
text of a traditional ChangeLog entry for that commit.
How can I see what is part of the proposed commit (message) and what is
not during patch review?
If we take `git format-patch` as a baseline, that means the subject
line is the first line of the commit message, and everything in the
email body up to the first line of the actual diff is the commit
message. But sometimes one wants to say things in the email that
aren't going to go into the commit message. I don't have a good
suggestion for how to handle that, ...
Git already has a way to do that. The submitter can write anything they want to
between the '---' and 'diff ...'
That is '---' ends the commit message.