[The following is a form letter.]
Hello,
You recently sent a message to a Debian Project mailing list to which I am
subscribed, and also included me in the To or CC header.
Please don't do this. The Debian Mailing List Code of Conduct says:
When using the Debian mailing lists, please follow these rules:
[...]
* When replying to messages on the mailing list, do not send a carbon
copy (CC) to the original poster unless they explicitly request to be
copied.
(You can review the entire Debian Mailing List Code of Conduct at
<URL:http://www.debian.org/MailingLists/>.)
Rationally interpreted, this of course includes anything that works
equivalently to a CC, such including the original poster in the To: or Bcc:
headers, forwarding the message to the original poster, or using the
"bounce" feature of some mailers to send the message again, but rewriting the
SMTP envelope to address the original poster instead of the list.
Some people feel that it is best to send email to everyone who might
possibly be interested in a message, indifferent to whom might be
subscribed to various mailing lists, be part of the expansion of various
mailing lists, be behind an SMTP exploder, and so forth -- in other words,
that it is the responsibility of the recipient of duplicate mail messages
to handle them.
The Debian Mailing List Code of Conduct does not endorse that philosophy.
There are proven limitations with using procmail rules to eliminate
duplicate message based on Message-ID, for instance. More importantly, the
Debian Mailing List Code of Conduct expects the *senders* of mail to
exercise discretion and good judgement; it does not place the burden of
pruning unwanted copies of mail messages upon the recipient. You can find
discussions of this aspect of the Mailing List Code of Conduct in the
Debian mailing lists themselves, if you are interested: please see
<URL:http://lists.debian.org/search.html> to perform a search.
The subject has come up several times over the past years, and time and
again, the existing policy has been affirmed as the wisest course of
action. Many people, myself included, use the Mail-Followup-To message
header, which is honored by mail user agents such as Mutt to control the
distribution of replies to mailing lists; using such a header, a person can
easily indicate that he does (or does not) want to be send copies of
replies to his message. You may want to use an MUA that honors this
header, as it is in fairly wide usage on the Debian mailing lists, and may
help you avoid mistakes resulting in inadvertent violations of Debian's
Mailing List Code of Conduct.
Thank you.
On Sat, Jan 31, 2004 at 04:27:15PM +0100, Sven Luther wrote:
> On Fri, Jan 30, 2004 at 03:15:29PM +1100, Daniel Stone wrote:
> > On Thu, Jan 29, 2004 at 10:48:09PM -0500, X Strike Force SVN Repository Admin wrote:
> > > +* package the driver SDK.
> > > + + being worked on in people/daniel.
> >
> > Given I can't commit, and didn't work on it for ages before I got kicked
> > out, this is kind of (very) misleading.
>
> Yes indeed. I sent Branden a clean patch a few month ago, and he said he
> would apply it post 4.3.0-1, so i hope this would be fixed in a few
> days/weeks, whatever.
>
> I just hope Branden didn't loose the patch or something, as i would hate
> to have to redo it a third time because of it getting lost when i did
> it.
Mailing a patch to the BTS is a better way of ensuring it doesn't get
lost.
--
G. Branden Robinson | If you make people think they're
Debian GNU/Linux | thinking, they'll love you; but if
branden@debian.org | you really make them think, they'll
http://people.debian.org/~branden/ | hate you. -- Don Marquis
Attachment:
signature.asc
Description: Digital signature