public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Re: Small irritation: Can people please stop	sending their posts in duplicate...
Date: Wed, 02 Mar 2005 13:52:45 -0800	[thread overview]
Message-ID: <422635AD.1000403@gentoo.org> (raw)
In-Reply-To: <1109788683.9520.100.camel@cgianelloni.nuvox.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Gianelloni wrote:
| On Wed, 2005-03-02 at 13:12 -0500, Colin Kingsley wrote:
|
|>What I gather from this thread is that not every mailing list is
|>perfect, and not every mail client is perfect, so every now and then,
|>somebody gets a duplicate mail. Not the end of the world. Get over it.
|
|
| Yes, but when you deliberately have the EXACT SAME LIST in both the TO
| and the CC field, it is really annoying and your own fault for causing
| more list traffic.
|
|
|>What I would like clarified is what is the propper address for gentoo
|>mailing lists now? <list>@robin.gentoo.org, or <list>@gentoo.org. Or
|>are both ok?
|
|
| You can send to either one.

It's pretty clear that sending to something that abstracts the
implementation (in this case, which box the lists are hosted on) is
better -- therefore, either @lists.gentoo.org (does this exist?) or
@gentoo.org, not @robin.gentoo.org.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCJjWsXVaO67S1rtsRAtSQAKCzdh193OhcAOHbVA9XbMKVLlVmJQCgjVy0
20hgATLrzUzZ3dAmg4v3yR0=
=yRBt
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-03-02 21:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28 13:29 [gentoo-dev] Small irritation: Can people please stop sending their posts in duplicate Stuart Longland
2005-02-28 14:53 ` 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 [this message]
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=422635AD.1000403@gentoo.org \
    --to=spyderous@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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