Re: Adding commit details to SGML release notes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Adding commit details to SGML release notes
Date
Msg-id 1486.1440797558@sss.pgh.pa.us
Whole thread Raw
In response to Re: Adding commit details to SGML release notes  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Adding commit details to SGML release notes  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> 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 everyone?

> Since it's only needed by people preparing the release notes, I would
> guess it's okay --- evidently Tom was able to use it.

Well, that's only because I'm running a hand-installed git rather than
what RHEL6 comes with.

> Maybe an option is to use trunc when git 1.8.3 or newer is detected, and
> plain (no trunc) otherwise?

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 option
("git_changelog --short", or so), and that would dodge any concerns about
failing on git versions without the feature.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Adding commit details to SGML release notes
Next
From: Bruce Momjian
Date:
Subject: Re: Adding commit details to SGML release notes