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

From Bruce Momjian
Subject Re: Deriving release notes from git commit messages
Date
Msg-id 201107120202.p6C22xw09729@momjian.us
Whole thread Raw
In response to Re: Deriving release notes from git commit messages  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Martijn van Oosterhout <kleptog@svana.org> writes:
> > On Sat, Jul 02, 2011 at 03:45:03PM -0400, Robert Haas wrote:
> >>> There are git notes which you can attach to a commit after the fact... I like
> >>> the fact that they would keep the information in the repository (where they
> >>> seem to belong).
> 
> >> Yeah, but I think it's still basically append-only, which is kind of a
> >> nuisance, and it means they can only be updated by committers, which
> >> is not particularly helpful from my point of view.
> 
> > The documentation says:
> > "This command allows you to add/remove notes to/from objects, without
> > changing the objects themselves."
> 
> > So it doesn't appear append only. I think the idea is that every object
> > can have one note. How that works with versioning I have no idea.
> 
> A look at the git-notes man page says that you can only have one note
> per commit, but you can edit that note, and git does track the revision
> history of each note.
> 
> I think that we should adopt "git notes" as a better solution than
> making dummy whitespace changes when we want to put a commit-message
> correction into the commit history (you listening, Bruce?).

Yes, I heard.  I don't think I have done that since we moved to git.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: relpersistence and temp table
Next
From: Robert Haas
Date:
Subject: Re: relpersistence and temp table