Re: CVS commit messages and backpatching - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: CVS commit messages and backpatching
Date
Msg-id 200609132034.k8DKYLi07060@momjian.us
Whole thread Raw
In response to Re: CVS commit messages and backpatching  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: CVS commit messages and backpatching  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Andrew Dunstan wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> >> Bruce Momjian <bruce@momjian.us> writes:
> >> > I pull activity only from HEAD, so I do not see that tag.  In fact, I
> >> > use our src/tools/pgcvslog rather than cvslog.
> >>
> >> Not sure why we are maintaining our own script when there are much
> >> better things out there:
> >> http://freshmeat.net/projects/cvs2cl.pl/
> >
> > Well, my script produces output that is closer to what I need to create
> > the release notes.
> >
> 
> 
> If there are procedures, please document them. Nobody ever told me much
> when I was given committer status, and I just did what it looked like you
> guys did, and no doubt made some mistakes.

I guess the question is whether it is possible using cvs2cl to show only
HEAD, and then show if the same commit message also appears in the most
recent back branch.  And will that always work reliably?

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Getting a move on for 8.2 beta
Next
From: Tom Lane
Date:
Subject: Re: Lock partitions