public inbox for [email protected]
help / color / mirror / Atom feedFrom: Alvaro Herrera <[email protected]>
To: Jiangshan Liu <[email protected]>
Cc: [email protected]
Subject: Re: Ask about bug numbering rules in pgsql-bugs mailing list
Date: Thu, 7 Mar 2024 15:19:09 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <ALkA9gCSHr8BVMB6m*[email protected]>
On 2024-Mar-07, Jiangshan Liu wrote:
> Hello!
> I'm writing my thesis expecting to refer to commit issues on the PostgreSQL website pgsql-bugs mailing list via bug numbering, but I'm concerned that some of the commit issues are not numbered (e.g., https://www.postgresql.org/message-id/flat/1958255.PYKUYFuaPT%40aivenlaptop#1bdd1e237c4858f85b031352... ), and I'm curious about this, so I'd like to ask you for what reason this is happening, please! Thank you
We have a web interface to report bugs, which assigns numbers to them;
this interface simply copies the text to an email to the pgsql-bugs
mailing list, including the assigned number. However, many bugs are
reported not via the web interface but instead by direct email to the
same pgsql-bugs mailing list or even to another one (frequently
pgsql-hackers, but others too); these do not get any number. That's
exactly what happened in the case you quote.
We don't have a central bug tracking system.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Ask about bug numbering rules in pgsql-bugs mailing list
In-Reply-To: <[email protected]>
* 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