Re: pgsql: git_topo_order script, to match up commits across branches.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, "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-25 23:32:09
Message-ID: 3641.1285457529@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> +1 to git_changelog anyway.

That seems to be the consensus position, so done.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-09-25 23:33:44 pgsql: Rename git_topo_order -> git_changelog, per discussion.
Previous Message Tom Lane 2010-09-25 23:04:28 pgsql: Fix another join removal bug: the check on PlaceHolderVars was w

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-09-26 03:03:35 Re: What happened to the is_<type> family of functions proposal?
Previous Message José Arthur Benetasso Villanova 2010-09-25 22:55:02 Patch: Extend NOT NULL representation to pg_constraint