| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marti Raudsepp <marti(at)juffo(dot)org>, PostgreSQL www <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: searching for git commit hash |
| Date: | 2012-09-26 02:10:09 |
| Message-ID: | CABUevEzVe5VcgKGDJwoe5gW_Yx3nZ5xiHT++sLGDKEVMZOeKNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Tue, Sep 25, 2012 at 11:34 PM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)fr> wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> 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.
Are you talking about a simple "git branch -a --contains=<hash>"?
That only works if the hash is the same of course - not if the patch
was different in a back branch.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-09-26 02:52:12 | Re: searching for git commit hash |
| Previous Message | Magnus Hagander | 2012-09-26 01:02:58 | Re: Updates "What's New" URL |