From: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. |
Date: | 2010-09-26 19:45:28 |
Message-ID: | AANLkTinzqN5CmEB6CV1sbTYXBQfEy6A7vZwNFb_yiV32@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Sun, Sep 26, 2010 at 3:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(dot)gurjeet(at){ gmail | yahoo }.com
Twitter/Skype: singh_gurjeet
Mail sent from my BlackLaptop device
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-26 20:38:23 | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. |
Previous Message | Tom Lane | 2010-09-26 19:27:41 | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-26 19:45:32 | Re: do we want to gitignore regression-test-failure files? |
Previous Message | Tom Lane | 2010-09-26 19:27:41 | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. |