public inbox for [email protected]
help / color / mirror / Atom feedFrom: Dimitri Fontaine <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Marti Raudsepp <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: searching for git commit hash
Date: Tue, 25 Sep 2012 23:34:01 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEwY5tHy=fCZU=aGZx3vyHTxwxDyq-U0Hkzy8X=mgr4GFg@mail.gmail.com>
References: <[email protected]>
<CABUevEzpDFk=N9nN1FLuz8XJZgMcQ2v3aTFM-SiGcFwwByQgog@mail.gmail.com>
<CABRT9RC2TcibvR23z9LABrvwnCYVAMsav-kUJxvcqDK2KXGWCg@mail.gmail.com>
<[email protected]>
<CABUevEx+vPFyMO_PTZ6MN97F6wSwJKzc7DcBgrwbyZgAETfnFg@mail.gmail.com>
<[email protected]>
<CABUevEwY5tHy=fCZU=aGZx3vyHTxwxDyq-U0Hkzy8X=mgr4GFg@mail.gmail.com>
Magnus Hagander <[email protected]> writes:
> Added to http://www.postgresql.org/developer/coding/.
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.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
view thread (19+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: searching for git commit hash
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox