From: Avi Kivity <avi@qumranet.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
kvm-devel@lists.sourceforge.net,
Laurent Vivier <Laurent.Vivier@bull.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>,
cotte@de.ibm.com
Subject: Re: List stripping out cc's
Date: Sun, 19 Aug 2007 23:10:35 +0300 [thread overview]
Message-ID: <46C8A3BB.5020505@qumranet.com> (raw)
In-Reply-To: <46C89FCA.3010802@garzik.org>
Jeff Garzik wrote:
> Avi Kivity wrote:
>> Heiko Carstens wrote:
>>>> The only thing remotely relevant in the list config is that
>>>> 'Filter out duplicate messages to list members (if possible)' is
>>>> set as a default for new members. Maybe this means that if a cc
>>>> is also part of the list, that cc is stripped (which seems a wierd
>>>> implementation; I'd have expected that cc be kept and just one
>>>> copy sent out).
>>>>
>>>> Anybody have a clue?
>>>>
>>>
>>> I got also removed when I was cc'ed. IIRC that started when I
>>> subscribed to
>>> the list. So it looks like people who are subscribed to the list get
>>> removed from the cc list.
>>> That's very annoying btw. ;)
>>>
>>
>> I think I see what is happening. The list gets a message that you
>> are copied on. It sees you have opted not to receive duplicates, it
>> strips you from the cc list, since it knows that you will receive
>> another copy by direct routing (outside the list).
>
> Well, there is also /quite/ the problem with the Mail-Followup-To
> header, which causes most mailers to ignore the preferences of the
> community in favor of the preferences of the message author -- which
> totally screws up traditional To/CC handling on LKML.
>
Sorry, this was about kvm-devel, not lkml -- I should have taken
linux-kernel off the cc list here to avoid increasing confusion.
Somehow that felt wrong in an email about the evils of stripping out the
cc list.
I don't think there's an issue with M-F-T: here.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2007-08-19 20:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 15:58 [PATCH 0/2][KVM] guest time accounting Laurent Vivier
2007-08-13 8:01 ` [kvm-devel] " Avi Kivity
2007-08-13 8:13 ` Laurent Vivier
2007-08-13 8:38 ` Avi Kivity
2007-08-13 13:08 ` Laurent Vivier
2007-08-13 13:22 ` Avi Kivity
2007-08-13 14:15 ` Christian Borntraeger
2007-08-13 14:19 ` Avi Kivity
2007-08-13 14:26 ` Christian Borntraeger
2007-08-13 14:37 ` Avi Kivity
2007-08-13 20:40 ` Heiko Carstens
2007-08-19 9:32 ` List stripping out cc's (was: Re: [kvm-devel] [PATCH 0/2][KVM] guest time accounting) Avi Kivity
2007-08-19 19:53 ` List stripping out cc's Jeff Garzik
2007-08-19 20:10 ` Avi Kivity [this message]
2007-08-13 14:05 ` [kvm-devel] [PATCH 0/2][KVM] guest time accounting Christian Borntraeger
2007-08-13 14:10 ` Avi Kivity
2007-08-13 14:22 ` Christian Borntraeger
2007-08-13 14:22 ` Laurent Vivier
2007-08-13 14:30 ` Avi Kivity
2007-08-13 14:41 ` Laurent Vivier
2007-08-13 15:22 ` Christian Borntraeger
2007-08-13 15:36 ` Laurent Vivier
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=46C8A3BB.5020505@qumranet.com \
--to=avi@qumranet.com \
--cc=Laurent.Vivier@bull.net \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jeff@garzik.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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