| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(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-25 21:56:52 |
| Message-ID: | m21uhp6a1n.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> That's what I use. What about it doesn't work for you?
I don't remember how to summon it properly so it keeps barking at me.
Mmmm, I did try to have the information reported for a single commit,
though.
./src/tools/git_changelog --since '2012-09-14 00:00:00' --oldest-first --details-after
fatal: ambiguous argument 'master..origin/REL9_2_STABLE': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions
git log --format=fuller --date=iso --since=2012-09-14 00:00:00 --parents
master..origin/REL9_2_STABLE failed at ./src/tools/git_changelog line
141.
Well, I would like having the information on the web. Ideally at the
same place where we can browse the commit logs (gitweb), if not from
somewhere else where it's easy to grasp.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-25 22:10:09 | Re: searching for git commit hash |
| Previous Message | Tom Lane | 2012-09-25 21:52:03 | Re: searching for git commit hash |