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

On Sun, Sep 26, 2010 at 4:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I 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.
>
> Hah, I have a plan.  Let's just run git log for "master..RELx_y_STABLE"
> for each branch, rather than all the way back.  Then we can identify the
> sprout point as the parent of the last emitted commit for the branch.
> The "post dated" or "double tagged" or whatever you call 'em branch
> annotations for earlier master commits can then be inserted by hand,
> rather than reverse-engineering them by matching author/message/etc.
> This should be both faster and more reliable than the current method.

This doesn't seem more reliable to me in any way. Looking at the
actual commit history must surely be more reliable than assuming you
know what it is. I think what you should be doing is using git log
--decorate and extracting the information from that as you go by.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company