Re: pgsql: Improve draft release notes.

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Improve draft release notes.
Date: 2013-12-02 17:49:14
Message-ID: 20131202174914.GA15336@awork2.anarazel.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 2013-12-02 12:44:56 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > What does this text mean in the SGML?
>
> > +<!--
> > +Author: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2013-12-02 17:52:09 pgsql: doc: update wording of ineffective SET and ABORT commands
Previous Message Tom Lane 2013-12-02 17:44:56 Re: pgsql: Improve draft release notes.