Peter Eisentraut <peter_e@gmx.net> writes:
> On 2/3/15 10:11 AM, Marko Tiikkaja wrote:
>> And now that we're on the subject of ponies, it would be nice if the
>> relevant git hashes were included as well.
> That's probably not going to happen. A release-note entry is often the
> combination of many commits, and accurately tracking those is a lot of work.
Well, actually, modern release note entries tend to look like
<!--
Author: Andres Freund <andres@anarazel.de>
Branch: master [3fabed070] 2015-01-07 00:19:37 +0100
Branch: REL9_4_STABLE [7da102154] 2015-01-07 00:24:58 +0100
Author: Andres Freund <andres@anarazel.de>
Branch: master [31912d01d] 2015-01-07 00:18:00 +0100
Branch: REL9_4_STABLE [84911ff51] 2015-01-07 00:24:47 +0100
-->
<listitem> <para> Assorted fixes for logical decoding (Andres Freund) </para> </listitem>
because they're prepared on the basis of src/tools/git_changelog output
and so having the git hashes is merely a matter of not deleting that
info after we're done writing the user-visible text. So I could imagine
some tool that presents that info. I'm not volunteering to write it
though ...
regards, tom lane
