Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Date
Msg-id AANLkTinzqN5CmEB6CV1sbTYXBQfEy6A7vZwNFb_yiV32@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Sep 26, 2010 at 3:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
We could perhaps fix that if there were an inexpensive way to get the
SHA1 of the master commit that each branch is sprouted from.  However,
I'm inclined to propose that we instead manually place a tag at each
sprout point.  Any thoughts about that?  In particular, what should
the naming convention for such tags be?  I would have liked to use
RELx_y, but that's out because before 8.0 we named the initial
releases that way.


SPLITx_y, STAMPx_y, BRANCHx_y

--
gurjeet.singh
@ EnterpriseDB - The Enterprise Postgres Company
http://www.EnterpriseDB.com

singh.gurjeet@{ gmail | yahoo }.com
Twitter/Skype: singh_gurjeet

Mail sent from my BlackLaptop device

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: do we want to gitignore regression-test-failure files?
Next
From: Tom Lane
Date:
Subject: Re: Patch: Extend NOT NULL representation to pg_constraint