Re: Detailed release notes - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Detailed release notes
Date
Msg-id 73E3B3EA-12ED-4D99-ADB6-55253D3EA9BA@yesql.se
Whole thread Raw
In response to Re: Detailed release notes  (Marcos Pegoraro <marcos@f10.com.br>)
Responses Re: Detailed release notes
List pgsql-hackers
On 5 Aug 2024, at 13:16, Marcos Pegoraro <marcos@f10.com.br> wrote:

Em seg., 5 de ago. de 2024 às 07:54, jian he <jian.universality@gmail.com> escreveu:

[commitId_link1, commitId_link2]: Change functions to use a safe
search_path during maintenance operations (Jeff Davis)

I don't like that prefix dirtying each item. 

I too would prefer links at the end, not least since we might have 2 or 3 (or
more) links for an item.

Python also links to the Github issue and not the commit, in our project the
analog to that would be linking to the thread in the mailinglist archive as
well as the commit.  For us linking to the commit is probably preferrable since
it will link to the thread but the thread often wont link to the commit (like a
Github issue will).  Maybe icons for code/emailthread can be used to make it
clear what the link is, and cut down to horizontal space required?

--
Daniel Gustafsson

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH] Add crc32(text) & crc32(bytea)
Next
From: Joe Conway
Date:
Subject: Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?