Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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 17:25:43
Message-ID: 11280.1285521943@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers 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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2010-09-26 17:28:57 Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Previous Message Tom Lane 2010-09-26 16:42:22 Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-09-26 17:28:57 Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Previous Message Thom Brown 2010-09-26 17:07:32 Re: Additional index entries and table sorting