From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OT: why cc:?
Date: Sun, 15 Oct 2006 10:28:37 +1000 [thread overview]
Message-ID: <20061015002837.GA12632@twibble.org> (raw)
In-Reply-To: <432beae0610141538p3b722a9bx552942eeac2d44ff@mail.gmail.com>
On Sat, Oct 14, 2006 at 03:38:57PM -0700, "Justin Patrin" wrote:
> On 10/14/06, Koen Kooi <koen@dominion.kabel.utwente.nl> wrote:
> > Michael 'Mickey' Lauer schreef:
> > > Out of interest, why are you cc'ing to
> > > openembedded-devel@openembedded.org? That way we get duplicated mails.
> > > Please only use openembedded-devel@lists.openembedded.org -- the shorter
> > > form only works by coincidance -- it's not intented.
Why doesn't openembedded-devel@openembedded.org work? It seems silly
to have to put the lists bit in the email address and it's certainly
not common.
[...]
> As for the reply-all, if people would stop e-mailing the non-"lists"
> addresses this problem would go away.
What are these non-"lists" address you talk about and what are these
duplicates? I don't seem to see any?
--
Jamie Lenehan <lenehan@twibble.org>
next prev parent reply other threads:[~2006-10-15 0:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 16:51 [RFC] handhelds-pxa-2.6 -> linux-handhelds-2.6 Paul Sokolovsky
2006-10-13 17:13 ` Koen Kooi
2006-10-23 17:03 ` Paul Sokolovsky
2006-10-13 17:34 ` Erik Hovland
2006-10-14 13:23 ` Paul Sokolovsky
2006-10-14 15:11 ` Erik Hovland
2006-10-14 15:17 ` pHilipp Zabel
2006-10-14 15:35 ` Erik Hovland
2006-10-14 19:35 ` OT: why cc:? (was: [RFC] handhelds-pxa-2.6 -> linux-handhelds-2.6) Michael 'Mickey' Lauer
2006-10-14 19:41 ` OT: why cc:? Koen Kooi
2006-10-14 22:38 ` Justin Patrin
2006-10-15 0:28 ` Jamie Lenehan [this message]
2006-10-15 0:31 ` Jamie Lenehan
2006-10-15 8:40 ` Michael 'Mickey' Lauer
2006-10-21 12:02 ` [RFC] handhelds-pxa-2.6 -> linux-handhelds-2.6 Paul Sokolovsky
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=20061015002837.GA12632@twibble.org \
--to=lenehan@twibble.org \
--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.