Re: Deriving release notes from git commit messages - Mailing list pgsql-hackers

From David Christensen
Subject Re: Deriving release notes from git commit messages
Date
Msg-id 93D576D9-2325-46E1-BA3F-1022965F498F@endpoint.com
Whole thread Raw
In response to Re: Deriving release notes from git commit messages  (Christopher Browne <cbbrowne@gmail.com>)
List pgsql-hackers
On Jun 24, 2011, at 2:28 PM, Christopher Browne wrote:
> On Fri, Jun 24, 2011 at 6:47 PM, Greg Smith <greg@2ndquadrant.com> wrote:
>> On 06/24/2011 01:42 PM, Robert Haas wrote:
>>> I am not inclined to try to track sponsors in the commit message at
>>> all.
>> 
>> I was not suggesting that information be part of the commit.  We've worked
>> out a reasonable initial process for the people working on sponsored
>> features to record that information completely outside of the commit or
>> release notes data.  It turns out though that process would be easier to
>> drive if it were easier to derive a feature->{commit,author} list
>> though--and that would spit out for free with the rest of this.  Improving
>> the ability to do sponsor tracking is more of a helpful side-effect of
>> something that's useful for other reasons rather than a direct goal.
> 
> In taking a peek at the documentation and comments out on the interweb
> about "git amend," I don't think that it's going to be particularly
> successful if we try to capture all this stuff in the commit message
> and metadata, because it's tough to guarantee that *all* this data
> would be correctly captured at commit time, and you can't revise it
> after the commit gets pushed upstream.

Perhaps `git notes` could be something used to annotate these:

http://www.kernel.org/pub/software/scm/git/docs/git-notes.html

Regards,

David
--
David Christensen
End Point Corporation
david@endpoint.com






pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch
Next
From: Peter Eisentraut
Date:
Subject: Re: pg_upgrade defaulting to port 25432