From: Karl O. Pinc <kop@meme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] The way the list manages patch submission
Date: Sat, 04 Aug 2012 11:58:23 -0500 [thread overview]
Message-ID: <1344099503.12337.5@mofo> (raw)
In-Reply-To: <20120804133550.0107920022C@gemini.denx.de> (from wd@denx.de on Sat Aug 4 08:35:49 2012)
On 08/04/2012 08:35:49 AM, Wolfgang Denk wrote:
> Your registration in the mailing list has the "nodupes" flag set,
> which is documented as:
>
> Avoid duplicate copies of messages?
>
> When you are listed explicitly in the To: or Cc: headers of a
> list message, you can opt to not receive another copy from the
> mailing list. Select Yes to avoid receiving copies from the
> mailing list; select No to receive copies.
>
> If the list has member personalized messages enabled, and you
> elect to receive copies, every copy will have a
> X-Mailman-Copy: yes header added to it.
>
> You selected that you don't want dupes, so you should not complain
> that you don't get dupes.
FYI. I got the above message twice. Probably because you
sent the message To: me and Cc:-ed the list instead of
sending the message To: the list and cc:-ing me.
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
next prev parent reply other threads:[~2012-08-04 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 18:26 [U-Boot] The way the list manages patch submission Karl O. Pinc
2012-08-03 20:43 ` Andy Sharp
2012-08-03 21:12 ` Karl O. Pinc
2012-08-03 21:45 ` Graeme Russ
2012-08-03 22:46 ` Wolfgang Denk
2012-08-04 0:56 ` Karl O. Pinc
2012-08-04 13:35 ` Wolfgang Denk
2012-08-04 16:55 ` Karl O. Pinc
2012-08-04 23:08 ` Wolfgang Denk
2012-08-05 9:15 ` Alexander Holler
2012-08-04 16:58 ` Karl O. Pinc [this message]
2012-08-04 17:00 ` Karl O. Pinc
-- strict thread matches above, loose matches on Subject: below --
2012-08-04 13:37 Wolfgang Denk
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=1344099503.12337.5@mofo \
--to=kop@meme.com \
--cc=u-boot@lists.denx.de \
/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.