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

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Date
Msg-id 11280.1285521943@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
List pgsql-hackers
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?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: C function to return tuple
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.