Received: from magus.postgresql.org ([87.238.57.229])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <tgl@sss.pgh.pa.us>) id 1TGd34-0006Ud-U8
	for pgsql-www@postgresql.org; Tue, 25 Sep 2012 21:52:10 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <tgl@sss.pgh.pa.us>) id 1TGd31-0004MJ-Q4
	for pgsql-www@postgresql.org; Tue, 25 Sep 2012 21:52:10 +0000
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q8PLq33m000330;
	Tue, 25 Sep 2012 17:52:04 -0400 (EDT)
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
cc: Magnus Hagander <magnus@hagander.net>, Bruce Momjian <bruce@momjian.us>,
	Marti Raudsepp <marti@juffo.org>, PostgreSQL www <pgsql-www@postgresql.org>
Subject: Re: searching for git commit hash
In-reply-to: <m2bogt6b3q.fsf@2ndQuadrant.fr>
References: <20120530003133.GB24440@momjian.us>
	<CABUevEzpDFk=N9nN1FLuz8XJZgMcQ2v3aTFM-SiGcFwwByQgog@mail.gmail.com>
	<CABRT9RC2TcibvR23z9LABrvwnCYVAMsav-kUJxvcqDK2KXGWCg@mail.gmail.com>
	<29205.1338386624@sss.pgh.pa.us>
	<CABUevEx+vPFyMO_PTZ6MN97F6wSwJKzc7DcBgrwbyZgAETfnFg@mail.gmail.com>
	<20120902125407.GA24536@momjian.us>
	<CABUevEwY5tHy=fCZU=aGZx3vyHTxwxDyq-U0Hkzy8X=mgr4GFg@mail.gmail.com>
	<m2bogt6b3q.fsf@2ndQuadrant.fr>
Comments: In-reply-to Dimitri Fontaine <dimitri@2ndQuadrant.fr>
	message dated "Tue, 25 Sep 2012 23:34:01 +0200"
Date: Tue, 25 Sep 2012 17:52:03 -0400
Message-ID: <329.1348609923@sss.pgh.pa.us>
X-Pg-Spam-Score: -2.7 (--)
X-Archive-Number: 201209/46
X-Sequence-Number: 20981

Dimitri Fontaine <dimitri@2ndQuadrant.fr> writes:
> What I would like to have is the result of whatever tool is used those
> days to know which branches contain any given patch. I though that was
> ./src/tools/git_changelog but I can't seem to have that work here.

That's what I use.  What about it doesn't work for you?

			regards, tom lane