From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Detailed release notes |
Date: | 2024-08-05 13:33:17 |
Message-ID: | 73E3B3EA-12ED-4D99-ADB6-55253D3EA9BA@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 5 Aug 2024, at 13:16, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:
>
> Em seg., 5 de ago. de 2024 às 07:54, jian he <jian(dot)universality(at)gmail(dot)com <mailto:jian(dot)universality(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2024-08-05 13:36:21 | Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~? |
Previous Message | Aleksander Alekseev | 2024-08-05 13:19:45 | Re: [PATCH] Add crc32(text) & crc32(bytea) |