Re: Replying to a pgsql-committers email by CC'ing hackers

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Kevin Grittner <kgrittn(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Replying to a pgsql-committers email by CC'ing hackers
Date: 2016-04-29 17:20:40
Message-ID: 20160429172040.GA148836@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Bruce Momjian wrote:
>
> What is the recommended procedure for replying to a pgsql-committers
> messsage? Is cross-posting to hackers really the right approach, as it
> causes duplicate messages. (pgsql-committers CC removed.)

CCing pgsql-hackers when replying to -committers was discussed some
time ago and the consensus seemed to be that that's preferrable than
keeping the discussion in -committers only, because that one is so much
smaller. Whether -committers is kept in cc/to or not seems not to be
important. This is all in the archives somewhere ...

You must be new to this email thing.

Any millennial will tell you that there's no duplicate because Gmail
already de-duplicates them. You would only see one copy, ever.

Now, if you still live in a cave and don't use Gmail (like, say, me),
you could still change the options in Majordomo to send a unique copy of
each message, that is to say change the delivery class to "unique"
rather than "each". Then it will see that you have the same message in
two lists and send you only one.

Now, whenever you're in the CC list of a message (something which I'm
told is somewhat common around here) you would additionally get that
copy too! There's nothing majordomo could do about that of course.
Again the solution is to use Gmail (what else!). If you won't do that,
you can install a procmail recipe to remove the dupes, say

:0 Wh: msgid.lock
| formail -D 65536 $HOME/.msgid.cache

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Joshua D. Drake 2016-04-29 17:26:32 Re: Replying to a pgsql-committers email by CC'ing hackers
Previous Message Peter Eisentraut 2016-04-29 17:04:44 pgsql: doc: Minor wording changes

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2016-04-29 17:23:21 Re: Lets (not) break all the things. Was: [pgsql-advocacy] 9.6 -> 10.0
Previous Message Bruce Momjian 2016-04-29 17:01:21 Replying to a pgsql-committers email by CC'ing hackers