pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Euler Taveira <euler@eulerto.com>
To: Robert Haas <robertmhaas@gmail.com>
To: Marcos Pegoraro <marcos@f10.com.br>
Cc: jian he <jian.universality@gmail.com>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Detailed release notes
Date: Tue, 06 Aug 2024 12:02:59 -0300
Message-ID: <305b9225-297f-43de-b752-6ef47ee2b291@app.fastmail.com> (raw)
In-Reply-To: <CA+TgmoaM56sWpN=ED=K-ML1EnpU8Kf_d9Ktc=B1+pLLUcs8fNw@mail.gmail.com>
References: <CAB-JLwZnhaAcD2g_qxSqP-zcfek8NyOU48qqneeYcjwRODr6YA@mail.gmail.com>
	<F8C2CC64-5265-4668-901D-B4A20420EC89@yesql.se>
	<CAB-JLwYDP58XRTjQFGswBEBHokWSh00NbvFAsAVzSQgDr+hMFg@mail.gmail.com>
	<4D1ACBCD-70AD-4286-8640-6DFC2ED206B8@yesql.se>
	<1673965.1722003082@sss.pgh.pa.us>
	<CACJufxFFvo09kd1bCR0VuQoiyhj44hM6JSWzAvPFHMVMmXT+Xg@mail.gmail.com>
	<CAB-JLwbErUkZqcOXpf6vAy7EUBMgiHC3xB5oKdSOqjOMar8_Vw@mail.gmail.com>
	<73E3B3EA-12ED-4D99-ADB6-55253D3EA9BA@yesql.se>
	<8e5f43c4-ac1e-4085-9bd3-4c923b1b2d51@app.fastmail.com>
	<CACJufxE66E3DbCASq3oV8KE3MmNAwBpL2yNZR3zcp=TM+FvS=Q@mail.gmail.com>
	<CAB-JLwb-d5awcgHkeaNdHgJR61TXdRQto3zap0Ki4UnTVgwpSA@mail.gmail.com>
	<CA+TgmoaM56sWpN=ED=K-ML1EnpU8Kf_d9Ktc=B1+pLLUcs8fNw@mail.gmail.com>

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
> https://git.postgresql.org/pg/commitdiff/$COMMITID
> 
> 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

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=$COMMIT

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

https://www.postgresql.org/commit/da4017a694d

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

https://postgr.es/c/da4017a694d


--
Euler Taveira
EDB   https://www.enterprisedb.com/

view thread (74+ messages)  latest in thread

Message-ID: <305b9225-297f-43de-b752-6ef47ee2b291@app.fastmail.com>
Permalink:  ../305b9225-297f-43de-b752-6ef47ee2b291@app.fastmail.com/
Also on:    postgresql.org/message-id/305b9225-297f-43de-b752-6ef47ee2b291@app.fastmail.com

 · 

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: pgsql-hackers@postgresql.org
  Cc: euler@eulerto.com, robertmhaas@gmail.com, marcos@f10.com.br, jian.universality@gmail.com, daniel@yesql.se, tgl@sss.pgh.pa.us
  Subject: Re: Detailed release notes
  In-Reply-To: <305b9225-297f-43de-b752-6ef47ee2b291@app.fastmail.com>

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

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