Re: CVS commit messages and backpatching

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CVS commit messages and backpatching
Date: 2006-09-13 20:34:21
Message-ID: 200609132034.k8DKYLi07060@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> >> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-09-13 20:35:53 Re: Lock partitions
Previous Message Jim Nasby 2006-09-13 20:29:53 Re: Getting a move on for 8.2 beta