MIME-Version: 1.0
In-Reply-To: <13425.1522330858@sss.pgh.pa.us>
References: <1237101144.12611.1521809780021.JavaMail.zimbra@dbi-services.com>
 <d797feb3-1d31-3876-5e44-f485e13581fd@2ndquadrant.com>
 <b4167648-7ea5-ab14-06e3-34fe483ee88f@2ndquadrant.com>
 <5B6B7585-9892-4846-904F-BB5B4A011A7D@postgresql.org>
 <e2519cc3-f781-d111-26fd-ff5efa7648ad@2ndquadrant.com>
 <07C79745-DDD1-4544-B95F-D878A477E898@postgresql.org>
 <CABUevEw3sAROjdHW0OE4-i5+uM3VMHQTixtLT+SOWGJapYtaSw@mail.gmail.com>
 <13425.1522330858@sss.pgh.pa.us>
From: Magnus Hagander <magnus@hagander.net>
Date: Sun, 1 Apr 2018 17:55:21 +0200
Message-ID: 
 <CABUevEw9hB8r_WjZ2KHZej1NS79xnQ=3R=zDFtAYsEiJdhTGpg@mail.gmail.com>
Subject: Re: Blanks in the first line before the first word in the code boxes
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>,
	Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
	Daniel Westermann <daniel.westermann@dbi-services.com>,
 pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: multipart/alternative; boundary="001a1142acdc3528ab0568cb809e"
Precedence: bulk

--001a1142acdc3528ab0568cb809e
Content-Type: text/plain; charset="UTF-8"

On Thu, Mar 29, 2018 at 3:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Magnus Hagander <magnus@hagander.net> writes:
> > Is it possible that this issue actually showed up around 4-5 February,
> but
> > just has gone unnoticed since?
>
> It's been there a few weeks, anyway --- I remember somebody complaining
> before this particular thread started.  I wouldn't be a bit surprised
> if it broke then.
>

Yeah, it's quite likely that it got broken by the OS upgrade and nobody
picked up on it before then. This can probably be because the backbranch
documentation is only updated when we make actual releases.

However, why does devel work fine when the others are broken. It's the
exact same code that's run to load the docs. The *input* to the loader must
also be different at some point.

-- 
 Magnus Hagander
 Me: https://www.hagander.net/ <http://www.hagander.net/>
 Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

--001a1142acdc3528ab0568cb809e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Mar 29, 2018 at 3:40 PM, Tom Lane <span dir=3D"ltr">&lt;<a href=3D"mail=
to:tgl@sss.pgh.pa.us" target=3D"_blank">tgl@sss.pgh.pa.us</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex"><span class=3D"">Magnus Hagander &lt=
;<a href=3D"mailto:magnus@hagander.net">magnus@hagander.net</a>&gt; writes:=
<br>
&gt; Is it possible that this issue actually showed up around 4-5 February,=
 but<br>
&gt; just has gone unnoticed since?<br>
<br>
</span>It&#39;s been there a few weeks, anyway --- I remember somebody comp=
laining<br>
before this particular thread started.=C2=A0 I wouldn&#39;t be a bit surpri=
sed<br>
if it broke then.<br></blockquote><div><br></div><div>Yeah, it&#39;s quite =
likely that it got broken by the OS upgrade and nobody picked up on it befo=
re then. This can probably be because the backbranch documentation is only =
updated when we make actual releases.</div><div><br></div><div>However, why=
 does devel work fine when the others are broken. It&#39;s the exact same c=
ode that&#39;s run to load the docs. The *input* to the loader must also be=
 different at some point.</div></div><div><br></div>-- <br><div class=3D"gm=
ail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div>=C2=
=A0Magnus Hagander<br>=C2=A0Me: <a href=3D"http://www.hagander.net/" target=
=3D"_blank">https://www.hagander.net/</a><br>=C2=A0Work: <a href=3D"http://=
www.redpill-linpro.com/" target=3D"_blank">https://www.redpill-linpro.com/<=
/a></div></div></div>
</div></div>

--001a1142acdc3528ab0568cb809e--