public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Stephen Frost <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Dimitri Fontaine <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Jonathan S. Katz <[email protected]>
Cc: PostgreSQL WWW <[email protected]>
Subject: Re: mailing list redirect for bug numbers?
Date: Fri, 18 Jan 2019 13:17:52 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 2019-Jan-18, Stephen Frost wrote:

> > since copies received via a direct cc: rather than via the list would
> > lack the field.  (Hence, you're mistaken to claim this would be
> > locally searchable.)
> 
> Ok, it's only locally searchable for people who are subscribed to our
> mailing lists and keep local copies of the emails they get from our list
> server, but isn't that going to cover the vast majority of the people
> who are going to be looking in the commit log and trying to find a
> matching thread in their local archive..?

It doesn't work in that case either if you're CCed and you get the
direct copy before the list copy; that one won't have the header.
In my case I just deduplicate with formail/reformail and it simply
throws the second one away, and I suspect others do likewise.  I don't
know what does Gmail do.

> If we just agree to always use the message-ID of the first message in
> the thread when we're closing out a bug, and people are happy with using
> message-ID, then I'm not really sure what the bug # is doing for us (and
> I see that that question from my prior email wasn't answered).

Hmm, sometimes I refer to an intermediate message in a thread, not
necessarily the first, when something was discovered in the middle of
some discussion.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

view thread (32+ messages)  latest in thread

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], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: mailing list redirect for bug numbers?
  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