| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, 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-03 19:33:19 |
| Message-ID: | 201107032133.19548.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sunday, July 03, 2011 09:18:52 PM Magnus Hagander wrote:
> On Sun, Jul 3, 2011 at 20:04, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > On Sunday, July 03, 2011 06:46:15 PM Tom Lane wrote:
> >> 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 don't think its that hard to write a hook which allows notes changes
> > for a different set of people than source changes.
> > Whether the people wanting to annotate commits are ok with using git I do
> > not know.
>
> If you want a different group of people to maintain it, then why force
> it into the same repository in the first place? Having to write hooks
> to work around things with that seems to be solving the wrong problem,
> imho.
Because imho the information who worked on a patch belongs alongside the
patch. I can't forsee a really useful usage of that information without the
commit alongside...
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-07-03 20:07:40 | Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID |
| Previous Message | Magnus Hagander | 2011-07-03 19:18:52 | Re: Deriving release notes from git commit messages |