Re: Git ChangeLog policy for GCC Testsuite inquiry

["Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>]

On 07/02/2020 15:32, Segher Boessenkool wrote:
> On Fri, Feb 07, 2020 at 01:56:08PM +0000, Richard Earnshaw (lists) wrote:
> > On 07/02/2020 13:48, Segher Boessenkool wrote:
> > > Should we require some simple markup in the commit message before the
> > > changelogs?  Maybe
> > >
> > > CL gcc/
> > > 	* blablalba etc.
> > > CL gcc/testsuite/
> > > 	* gcc.target/...
> >
> > > etc.
> > >
> > > (Dunno if just "^CL " is too short?)
> >
> > I was thinking "@CL <dir>", but ^CL would work just as well.
>
> I meant ^ as in a regular expression, sorry for not being clear.

Ah! I think something more syntactically explicit would help avoid the 
risk of mis-parsing.

> > Any script should, in addition to extracting the author and email also
> > grep for "Co-authored-by:" annotations and add those as additional
> > contributors, of course.
>
> Is there no existing established practice for that?  (Or is this it and
> so infrquent that I never have seen it :-) )

It's a convention (much like signed-off-by, etc).  But it's fairly 
widely accepted.  In the git conversion we added fields for it where we 
detected co-authorship in the ChangeLog entries.  Git has no specific 
field for recording additional authors, so this approach addresses this 
and some tools know how to add the appropriate accreditation based on it.

https://git.wiki.kernel.org/index.php/CommitMessageConventions

Also "git help interpret-trailers"

R.


> Segher