Re: git log -> changelog

[Gary V. Vaughan]

[[sorry for the thread hijack]]

On 6 Sep 2010, at 03:44, Ralf Wildenhues wrote:
> * Eric Blake wrote on Thu, Sep 02, 2010 at 11:23:57PM CEST:
>> The git pages are clear that S-O-B has project-dependent
>> interpretation.  Coreutils currently doesn't even use it (the only
>> people with commit privileges to the master coreutils.git have FSF
>> copyright, and it is assumed that they are each trustworthy enough
>> to do due diligence in verifying that patches from other
>> contributors meet copyright rules, without relying on any markup in
>> the commit message itself).
>> 
>> But if we wanted, we could adopt a policy that S-O-B on GNU projects
>> using the gitlog-to-changelog conversion implies (partial)
>> authorship, above and beyond the --author.
> 
> Except that the autotools project logs contain lots of S-O-B entries
> which explicitly do not have that particular meaning.  :-/

I suppose we can create an annotation for logs that have a non-compliant
SoB as if it was any other commit log typo we want to override to make
sure gitlog-to-changelog creates a beautiful ChangeLog -- after we document
our policy, and for entries going back to the beginning of the year in
which we decide to start using gitlog-to-changelog.

Even if we wait until next year to start using gitlog-to-changelog, I
think it worthwhile to know in advance how we will cope with a commit log
that needs a correction.

Cheers,
-- 
Gary V. Vaughan (address@hidden)

PGP.sig
Description: This is a digitally signed message part