On Sun, Sep 26, 2010 at 1:25 PM, Tom Lane <tgl@sss.pgh.pa.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
