Re: Detailed release notes - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: Detailed release notes
Date
Msg-id 305b9225-297f-43de-b752-6ef47ee2b291@app.fastmail.com
Whole thread Raw
In response to Re: Detailed release notes  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Detailed release notes
List pgsql-hackers
On Tue, Aug 6, 2024, at 11:02 AM, Robert Haas wrote:
On Tue, Aug 6, 2024 at 9:57 AM Marcos Pegoraro <marcos@f10.com.br> wrote:
> Loved, except that the commit id does not help too much, so I don't think we need it.
> I think a numbered link would be better.

I think the commit ID is quite useful. If you're using git, you can do
"git show $COMMITID". If you're using the web, you can go to

Big -1 for removing the commit ID.

Agree. Numbers mean nothing in this context. You are searching for detailed
information about the referred feature. A visual information (commit hash)
provides a context that you will find the source code modifications for that
feature.

Talking about the patch, do we want to rely on an external resource? I suggest
that we use a postgresql.org subdomain. It can point to


or even better use a rewrite rule to define a user-friendly URL (and probably a
mechanism to hide the gitweb URL) like


and the short version that we usually use for the mailing list.



--
Euler Taveira

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin
Next
From: Michael Paquier
Date:
Subject: Re: Thread-unsafe MD5 on big-endian systems with no OpenSSL