MIME-Version: 1.0
In-Reply-To: <f00bf53f-e6b5-a033-69be-0c63878f0d30@gmail.com>
References: <57179283.6080704@purtz.de>
 <20160503193441.GA61759@alvherre.pgsql>
 <CAF4Au4zUVOuWjWc+B72yvvpVo=TJad6=x9chig7Ls9DNa7Kgrg@mail.gmail.com>
 <db902495-52f2-ee33-b229-5fe094cf4937@2ndquadrant.com>
 <572AD007.60900@gmail.com>
 <bcc78f65-ef7f-22ea-0d7a-a83b7b7538b6@2ndquadrant.com>
 <5752E599.2090505@gmail.com>
 <de53dbdf-a0f1-5673-bbee-ca4f3d75f278@2ndquadrant.com>
 <576d0623-a89c-b3de-e321-dc48a579ff1a@2ndquadrant.com>
 <eb1abd5e-4210-b5c5-522c-d15e4e62a09b@gmail.com>
 <b4f74ac9-09ba-d198-092b-e2bfbf1c0194@2ndquadrant.com>
 <4adecfc6-2f2e-2ff2-bfa3-58b7d397227b@gmail.com>
 <c7e45017-c918-d2ec-a7e5-f696e41c5314@gmail.com>
 <e4e972b8-425b-164b-031e-f6db2daef9d2@2ndquadrant.com>
 <8f227b2a-5093-8d99-85da-ea00e18343f6@gmail.com>
 <aab72af9-928c-e116-d342-804bf78911c6@gmail.com>
 <449e34c4-9cc8-d17d-5ebe-be92b4c0a87a@gmail.com>
 <09b13d85-e259-2464-723a-467210264afe@2ndquadrant.com>
 <f00bf53f-e6b5-a033-69be-0c63878f0d30@gmail.com>
From: Thomas Munro <thomas.munro@enterprisedb.com>
Date: Mon, 11 Sep 2017 10:59:40 +1200
Message-ID: 
 <CAEepm=2s4a_skiJFeo8KcRdb7LQOkWhAG+M7WnK_4f0Rqq2jHw@mail.gmail.com>
Subject: Re: Docbook 5.x
To: Alexander Lakhin <exclusion@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
 Oleg Bartunov <obartunov@gmail.com>,
	Alvaro Herrera <alvherre@2ndquadrant.com>,
 =?UTF-8?Q?J=C3=BCrgen_Purtz?= <juergen@purtz.de>,
	pgsql-docs@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On Sat, Sep 9, 2017 at 12:30 AM, Alexander Lakhin <exclusion@gmail.com> wrote:
> Hello,
>
> 06.09.2017 18:54, Peter Eisentraut wrote:
>>
>>
>> I have started working through these patches now. I have committed the
>> escaping of < and & and will work through the rest slowly, to minimize
>> disruptions to other development.
>
> Great!
>
> I have rebased all the remaining patches and updated scripts for the current
> master (see attachment).

Hi Alexander,

In future versions of this patch set, if there is a dependency between
the patches would you mind indicating the order to apply them, perhaps
with prefixes like "0001-"?  That would be quite useful for humans who
aren't yet familiar enough with your patch set to guess the order, and
also for stupid patch testing robots:

== Fetched patches from message ID
f00bf53f-e6b5-a033-69be-0c63878f0d30%40gmail.com
== Applying on top of commit 3c435952176ae5d294b37e5963cd72ddb66edead
== Applying patches from tarball pg-doc.check.tar.bz2...
== Applying patch pg-doc.check/patches/sgml-xml/ecpg.patch...
== Applying patch pg-doc.check/patches/sgml-xml/func.patch...
== Applying patch
pg-doc.check/patches/sgml-xml/generate-errcodes-table.pl.patch...
== Applying patch pg-doc.check/patches/sgml-xml/pgtesttiming.patch...
== Applying patch pg-doc.check/patches/sgml-xml/release-10.patch...
1 out of 5 hunks FAILED -- saving rejects to file
doc/src/sgml/release-10.sgml.rej

Thanks!

-- 
Thomas Munro
http://www.enterprisedb.com


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs