public inbox for [email protected]  

help / color / mirror / Atom feed

From: Magnus Hagander <[email protected]>
To: Tom Lane <[email protected]>
Cc: Jonathan S. Katz <[email protected]>
Cc: Daniel Westermann (DWE) <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: PostgreSQL Documentation <[email protected]>
Subject: Re: Dead link in release notes for 19
Date: Mon, 27 Apr 2026 18:29:53 +0200
Message-ID: <CABUevExYdBvGJFt7Sv9r=ngsdpaLoEPp2YAsMZ1uRkoAF=1CFg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <ZR2PPFF1830B8774E019A0F6C5D6A00EB88D2362@ZR2PPFF1830B877.CHEP278.PROD.OUTLOOK.COM>
	<[email protected]>
	<ZR2PPFF1830B87786A5DD60DEF44FBF3E11D2362@ZR2PPFF1830B877.CHEP278.PROD.OUTLOOK.COM>
	<[email protected]>
	<[email protected]>

On Mon, 27 Apr 2026 at 16:37, Tom Lane <[email protected]> wrote:

> "Jonathan S. Katz" <[email protected]> writes:
> > On 4/27/26 3:55 AM, Daniel Westermann (DWE) wrote:
> >>> Strange, the link works for me.
> >>> It points to commit 2f094e7ac691abc9d2fe0f4dcf0feac4a6ce1d9c.
>
> >> Yes, now it works. This morning it gave some XML error.
>
> > When I clicked the link, the page errors,  but there's an error message
> > at the top:
>
> > ===
> > This page contains the following errors:
> > error on line 6484 at column 177: EntityRef: expecting ';'
> > Below is a rendering of the page up to the first error.
> > ===
>
> > I think this may be an issue with gitweb?
>
> Yeah, I got a rendering error too (yet a different one).  I think that
> commit is so large that we're running into browser rendering engine
> bugs.  Or maybe gitweb is failing to send it all.
>
>
It's working right now, but next time it fails, if someone can check with a
view source or similar if it happens to be that gitweb just cut off the
outputsomewhere in th emiddle without finishing it. That is, if it is a
HTML page but doesn't go all the way to </html>.

//Magnus

view thread (8+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Dead link in release notes for 19
  In-Reply-To: <CABUevExYdBvGJFt7Sv9r=ngsdpaLoEPp2YAsMZ1uRkoAF=1CFg@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox