Re: Deriving release notes from git commit messages

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Christopher Browne <cbbrowne(at)gmail(dot)com>
Subject: Re: Deriving release notes from git commit messages
Date: 2011-07-02 14:19:07
Message-ID: 201107021619.08614.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Saturday, July 02, 2011 06:10:43 AM Tom Lane wrote:
> I wouldn't have a problem with establishing a convention that we
> write credits in commit messages in a more standardized way, ie put
> something like "Author: Joe Blow <joe(at)blow(dot)nom>" in the body of the
> commit message. However, the points that were raised about commit
> messages being effectively uncorrectable after-the-fact seem to me
> to put a big crimp in the idea of using that as the primary source
> of credit information. We'd still need something like the web app
> Robert described in <BANLkTimOxDA08qM4LSH4QjA3YZtyuuewsA(at)mail(dot)gmail(dot)com>
> to allow correction of the info.
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).

Andres

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2011-07-02 15:51:13 clean.pl on Windows fails to remove flex output
Previous Message Simon Riggs 2011-07-02 12:32:04 Re: time-delayed standbys