Re: Managing multiple branches in git

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Managing multiple branches in git
Date: 2009-06-04 03:14:17
Message-ID: 200906040314.n543EHb16808@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > The only reason Tom sees a single line history is because he uses an
> > addon tool for CVS called cvs2cl: see <http://www.red-bean.com/cvs2cl/>.
> > It's not part of CVS, and I'm not sure how many others use it. I sure
> > don't.
>
> FWIW, I believe Bruce uses some version of it as well. It's our main
> tool for dredging up the raw data for release notes.

I use pgsql/src/tools/pgcvslog because it gives me exactly the
information I need for the release notes. It can even suppress items
that appeared in backbranch commits (because those changes already
appeared in a backbranch release).

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-06-04 04:09:05 Re: Synchronous replication: status of standby side
Previous Message Tatsuo Ishii 2009-06-04 02:45:57 Re: 8.4b2 tsearch2 strange error