Automating the maintenance of the ChangeLog file
Joseph Myers
joseph@codesourcery.com
Thu Nov 29 14:04:00 GMT 2018
On Thu, 29 Nov 2018, Florian Weimer wrote:
> I'm coming to this from a completely different angle. I want a way for
> contributors and reviewers to have a *reliable* to determine what the
> patch will look like in the repository. That includes both the diff
> *and* the commit message.
I think that should be the "git am" convention (subject header gives
summary line for the patch after removing any [PATCH ...] tag, body of
email is rest of commit message up to a "---" line or the patch itself).
(And that convention should be appropriate for emails generated by any
pull request / patch review system as well.)
--
Joseph S. Myers
joseph@codesourcery.com
More information about the Libc-alpha
mailing list