From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. |
Date: | 2010-09-26 17:28:57 |
Message-ID: | AANLkTi=MHWKSaw1wzW9CsNWh_MpR=Z+6atEY057fdhpN@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Sun, Sep 26, 2010 at 1:25 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
>> If we could figure out how to show which major release a master-branch
>> commit antedated, and which point release a back-branch commit
>> antedated, I think we would have something that's actually significantly
>> more useful for both purposes than either of these behaviors.
>
> I think we could get that behavior fairly easily by remembering the last
> tag matching one of the commits on a branch, as we chase the branch
> backwards. However, I'm not seeing a convenient way to extract the
> commit SHA1s pointed to by the available tags. git tag doesn't tell
> this and git show provides way too much information. Anybody know the
> right incantation for that?
git rev-parse REL8_3_0
But I still want an option for the original behavior. I have been
using it extensively and I like it.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-26 18:07:53 | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. |
Previous Message | Tom Lane | 2010-09-26 17:25:43 | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. |
From | Date | Subject | |
---|---|---|---|
Next Message | Marios Vodas | 2010-09-26 17:29:23 | Re: C function to return tuple |
Previous Message | Tom Lane | 2010-09-26 17:25:43 | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. |