From: "Justin Patrin" <papercrane@gmail.com>
To: OpenEmbedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Multiple mailing list addresses
Date: Mon, 9 Apr 2007 10:37:12 -0700 [thread overview]
Message-ID: <432beae0704091037s67b6eeb5kf145751af05d1969@mail.gmail.com> (raw)
The OE mailing list server is allow mail to be sent to either the
lists.openzaurus.org or openzaurus.org domains, causing confusion and
duplicate e-mails for those of us who are used to the technology being
smart enough to handle things correctly.
Could someone please make it so that one of the 2 is the allowed one
and the other bounces so that these problems can be squelched?
For example, both openembedded-devel@lists.openembedded.org and
openembedded-devel@openembedded.org work for this mailing list. When
someone sends mail to openembedded-devel@openembedded.org the list
then adds openembedded-devel@lists.openembedded.org to the headers and
a quick reply ends up going to both addresses.
--
Justin Patrin
next reply other threads:[~2007-04-09 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 17:37 Justin Patrin [this message]
2007-04-09 17:41 ` Multiple mailing list addresses Koen Kooi
2007-04-09 18:20 ` Matthias Hentges
2007-04-09 18:45 ` Justin Patrin
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=432beae0704091037s67b6eeb5kf145751af05d1969@mail.gmail.com \
--to=papercrane@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.