On Sat, Aug 29, 2015 at 12:23:30AM +0200, Andres Freund wrote:
> On 2015-08-28 17:49:35 -0400, Bruce Momjian wrote:
> > If we _don't_ do that, how do you easily get those lines into the
> > release notes? I can't imagine how hard it was for Andres to add that
> > text to the 9.5 release notes:
>
On 2015-08-28 17:49:35 -0400, Bruce Momjian wrote:
> If we _don't_ do that, how do you easily get those lines into the
> release notes? I can't imagine how hard it was for Andres to add that
> text to the 9.5 release notes:
Formatting the log wasn't the hard part, that was finding out which item
Bruce Momjian writes:
> On Fri, Aug 28, 2015 at 05:32:38PM -0400, Tom Lane wrote:
>> Personally I find that truncated output to be pretty unreadable, and
>> would strongly object to changing git_changelog so that that was the only
>> possible format. However, I have no objection to making it an o
On Fri, Aug 28, 2015 at 05:32:38PM -0400, Tom Lane wrote:
> Alvaro Herrera writes:
> > Bruce Momjian wrote:
> >> To simplify the creation of the release note with the commit tag as an
> >> SGML comment, I think src/tools/git_changelog should be modified to
> >> output this string. The format "tru
Alvaro Herrera writes:
> Bruce Momjian wrote:
>> To simplify the creation of the release note with the commit tag as an
>> SGML comment, I think src/tools/git_changelog should be modified to
>> output this string. The format "trunc" feature was added in git 1.8.3.
>> Is that old enough for every
Bruce Momjian wrote:
> To simplify the creation of the release note with the commit tag as an
> SGML comment, I think src/tools/git_changelog should be modified to
> output this string. The format "trunc" feature was added in git 1.8.3.
> Is that old enough for everyone?
Hmm, that's pretty new
