Re: [PATCH] gitlog-to-changelog: provide a ChangeLog-repair mechanism

[Jim Meyering]

Jim Meyering wrote:
> Eric Blake wrote:
>> On 11/01/2011 11:15 AM, Jim Meyering wrote:
>>> I've been thinking about this for years, ever since the unpleasantness
>>> of that first git commit that I mistakenly attributed to myself.
>>>
>>> With this new --amend=FILE option, you'll be able to maintain
>>> a list of<SHA,CODE+>  pairs where SHA is a 40-byte SHA1
>>> (alone on a line) referring to a commit in the current project, and
>>> CODE refers to one or more consecutive lines of Perl code.
>>> Pairs must be separated by one or more blank lines.
>>> Using that file, invoke gitlog-to-changelog with this new option,
>>> and it'll do the rest.
>>
>> Is there some way to use 'git notes' as a way of generating these
>> fixups as notes attached to the various commits they are meant to fix,
>> in a known namespace, and to thus generate FILE by doing a git notes
>> listing of all commits with an attached note?
>
> At least for now, I'd prefer not to rely on git notes, since we
> haven't established a policy for ensuring how to propagate them
> to the shared repository and how to handle merges.

After sleeping on it, I've concluded that I'll never want to use
git notes for this.  This process modifies the ChangeLog file, which is
a part of the release tarball.  As such, any inputs to that process
should be version-controlled, so that the tarball contents is uniquely
determined solely by data under version control.