From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-committers(at)postgresql(dot)org" <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: git_topo_order script, to match up commits across branches. |
Date: | 2010-09-24 21:34:10 |
Message-ID: | 2F98B6AB-9D32-4743-A586-22739C69FA61@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Sep 24, 2010, at 3:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <rhaas(at)postgresql(dot)org> writes:
>> git_topo_order script, to match up commits across branches.
>> This script is intended to substitute for cvs2cl in generating release
>> notes and scrutinizing what got back-patched to which branches.
>
> BTW ... I don't especially care for the name you picked for this script.
> The fact that it does a topological sort is an implementation detail
> that its users couldn't care less about, especially since that doesn't
> matter except for corner cases. How about "collate_git_log" or
> something along it.
I don't think that's any better - collate could mean anything - but I don't think it's any worse, either. Change it if you want.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-24 21:36:59 | Re: pgsql: git_topo_order script, to match up commits across branches. |
Previous Message | Tom Lane | 2010-09-24 19:32:45 | Re: pgsql: git_topo_order script, to match up commits across branches. |
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2010-09-24 21:34:13 | Re: snapshot generation broken |
Previous Message | Dimitri Fontaine | 2010-09-24 21:24:51 | Re: psql's \dn versus temp schemas |