Skip site navigation (1) Skip section navigation (2)

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: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: git_topo_order script, to match up commits across branches.
Date: 2010-09-24 19:32:45
Message-ID: 23645.1285356765@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
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 that line?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-09-24 19:41:47
Subject: Re: What happened to the is_<type> family of functions proposal?
Previous:From: Kevin GrittnerDate: 2010-09-24 19:22:48
Subject: Re: Serializable Snapshot Isolation

pgsql-committers by date

Next:From: Robert HaasDate: 2010-09-24 21:34:10
Subject: Re: pgsql: git_topo_order script, to match up commits across branches.
Previous:From: Robert HaasDate: 2010-09-24 18:37:22
Subject: pgsql: In levenshtein_internal(),describe algorithm a bit more clearly

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group