public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Longland <stuartl@longlandclan.hopto.org>
To: Gentoo Development List <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Small irritation: Can people please stop sending their posts in duplicate...
Date: Mon, 28 Feb 2005 23:29:40 +1000	[thread overview]
Message-ID: <42231CC4.5010000@longlandclan.hopto.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

Hi All,
	Sorry for the noise... but a number of people have started sending to
${LIST}@gentoo.org, CCing to ${LIST}@lists.gentoo.org -- resulting in
duplicate emails being sent to this end.

	If possible, can people kindly pick one, or the other -- and not both?

	Incidentally, I've fixed the problem with using robin.gentoo.org... I
could've filtered on other headers...but what I've done instead is put
the following in my .mailfilter file (Yes, I use maildrop here):

if (/Cc: *!.*!@.*.gentoo.org/)
{
         xfilter "sed -e 's/$MATCH3/@lists.gentoo.org/'"
}

if (/To: *!.*!@.*.gentoo.org/)
{
         xfilter "sed -e 's/$MATCH3/@lists.gentoo.org/'"
}

(There's probably a way to combine those into one... but I can't be
arsed looking. ;-)

Regards,
--
+-------------------------------------------------------------+
| Stuart Longland -oOo- http://stuartl.longlandclan.hopto.org |
| Atomic Linux Project     -oOo-    http://atomicl.berlios.de |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| I haven't lost my mind - it's backed up on a tape somewhere |
+-------------------------------------------------------------+

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

             reply	other threads:[~2005-02-28 13:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28 13:29 Stuart Longland [this message]
2005-02-28 14:53 ` [gentoo-dev] Small irritation: Can people please stop sending their posts in duplicate M. Edward (Ed) Borasky
2005-02-28 14:56   ` Lance Albertson
2005-02-28 23:32     ` Nick Rout
2005-02-28 19:55 ` Luke-Jr
2005-02-28 22:56   ` Mike Frysinger
2005-03-01  7:06     ` D. Wokan
2005-03-01  6:59 ` D. Wokan
2005-03-01  7:30   ` Anthony Gorecki
2005-03-01  7:37     ` Anthony Gorecki
2005-03-01  7:59   ` Stuart Longland
2005-03-01  8:20     ` Anthony Gorecki
2005-03-01  9:52       ` Stuart Longland
2005-03-01 12:17         ` Georgi Georgiev
2005-03-01 12:23           ` Georgi Georgiev
2005-03-01 15:02       ` Bill Davidson
2005-03-01 18:47         ` Maurice van der Pot
2005-03-02  1:26           ` Georgi Georgiev
2005-03-02  1:30             ` Georgi Georgiev
2005-03-02  9:45               ` Maurice van der Pot
2005-03-02 10:04             ` [gentoo-dev] " Torsten Veller
2005-03-02 14:36               ` Georgi Georgiev
2005-03-02 18:12                 ` Colin Kingsley
2005-03-02 18:12                   ` Colin Kingsley
2005-03-02 18:38                   ` Chris Gianelloni
2005-03-02 18:59                     ` Torsten Veller
2005-03-02 21:52                     ` Donnie Berkholz
2005-03-03  1:07                     ` Georgi Georgiev
2005-03-03 18:45       ` [gentoo-dev] " Alexander Simonov
2005-03-05 21:35       ` Benjamin A. Collins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

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

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42231CC4.5010000@longlandclan.hopto.org \
    --to=stuartl@longlandclan.hopto.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox