Re: pgsql: Improve draft release notes. - Mailing list pgsql-committers

From Andres Freund
Subject Re: pgsql: Improve draft release notes.
Date
Msg-id 20131202174914.GA15336@awork2.anarazel.de
Whole thread Raw
In response to Re: pgsql: Improve draft release notes.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Improve draft release notes.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On 2013-12-02 12:44:56 -0500, Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
> > What does this text mean in the SGML?
>
> > +<!--
> > +Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
> > +Branch: master [4c697d8f4] 2013-11-18 09:51:09 +0200
> > +Branch: REL9_3_STABLE [ea2bb1b47] 2013-11-18 10:16:31 +0200
> > +Branch: REL9_2_STABLE [3379263b6] 2013-11-18 10:12:22 +0200
> > +-->
>
> That's chunks of the git_changelog output I was working from.  I use it
> as a guide to know which changelog items should go into which back
> branches.  I'll strip the comments after I've finished making all the
> back-branch notes, but this is just a working copy at the moment.

FWIW I vote for leaving them in, even though it admittedly only helps
the few people looking at the sgml, it is quite useful information. I
wish it always had been in there.

Greetings,

Andres Freund

--
 Andres Freund                       http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Improve draft release notes.
Next
From: Bruce Momjian
Date:
Subject: pgsql: doc: update wording of ineffective SET and ABORT commands