Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OT: why cc:?
Date: Sun, 15 Oct 2006 10:31:48 +1000	[thread overview]
Message-ID: <20061015003148.GA12655@twibble.org> (raw)
In-Reply-To: <20061015002837.GA12632@twibble.org>

On Sun, Oct 15, 2006 at 10:28:37AM +1000, Jamie Lenehan wrote:
[...]
> What are these non-"lists" address you talk about and what are these
> duplicates? I don't seem to see any?

Oh, I think I see what those duplicates are now... I have had this in
my .procmailrc for ever:

 #
 # Weed out duplicates...
 #
 :0 Whc: $HOME/Mail/msgid.lock
 | formail -D 65536 $HOME/Mail/cache.dupes
 :0 a:
 dupes

which means I never see duplicates. So I take the duplicates you are
talking about happen from emails being sent to both
openembedded-devel@lists.openembedded.org and
openembedded-devel@openembedded.org ?

-- 
 Jamie Lenehan <lenehan@twibble.org>



  reply	other threads:[~2006-10-15  0:38 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
2006-10-15  0:31                   ` Jamie Lenehan [this message]
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=20061015003148.GA12655@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox