pgsql: Consistently indent release notes for prior releases.

Started by Bruce Momjianover 18 years ago3 messageshackers
Jump to latest
#1Bruce Momjian
bruce@momjian.us

Log Message:
-----------
Consistently indent release notes for prior releases.

Modified Files:
--------------
pgsql/doc/src/sgml:
release.sgml (r1.526 -> r1.527)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml?r1=1.526&r2=1.527)

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Bruce Momjian (#1)
Re: [COMMITTERS] pgsql: Consistently indent release notes for prior releases.

momjian@postgresql.org (Bruce Momjian) writes:

Consistently indent release notes for prior releases.

Bruce, if you don't revert that patch I will do it for you. Random
changes to the release.sgml sections for old releases are an utter
nightmare when it comes time to produce back-branch updates.

regards, tom lane

#3Bruce Momjian
bruce@momjian.us
In reply to: Tom Lane (#2)
Re: [COMMITTERS] pgsql: Consistently indent release notes for prior releases.

Tom Lane wrote:

momjian@postgresql.org (Bruce Momjian) writes:

Consistently indent release notes for prior releases.

Bruce, if you don't revert that patch I will do it for you. Random
changes to the release.sgml sections for old releases are an utter
nightmare when it comes time to produce back-branch updates.

The problem is that we use those back branches as templates for new
minor releases. I could have just done 8.2.X but I figured I should be
consistent.

I am not sure why it affects back branch updates. The way I create back
branches is to modify release.sgml in HEAD and then copy that file to
the back branches, and cutt off the top part of release.sgml for the
appropriate branch.

Also I also don't understand why you are threatening to revert it before
even complaining about it to me.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +