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>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Date: 2010-09-27 00:24:21
Message-ID: 20160.1285547061@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sun, Sep 26, 2010 at 4:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.

> 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.

I looked at doing that but it didn't seem like an improvement. Take
a look at the new version and see what you think.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2010-09-27 01:03:24 Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
Previous Message Tom Lane 2010-09-27 00:22:35 pgsql: Improve git_changelog as per discussion with Robert Haas.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-09-27 00:32:26 Re: forming tuple as an attribute inside another tuple in c function
Previous Message Fujii Masao 2010-09-26 23:29:08 Re: recovery.conf location