Re: [Qemu-block] [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open()
On Wed, Jun 10, 2015 at 10:37:10AM +0200, Kevin Wolf wrote: Am 09.06.2015 um 17:21 hat Eric Blake geschrieben: On 06/09/2015 08:48 AM, Stefan Hajnoczi wrote: I guess my @redhat.com email was received directly from Max because I was in CC list. It didn't pass through Mailman. I saw the original, unmodified list of CCs with Kevin included. The @gmail.com email was received from the mailing list. Mailman did what you described. And that's what makes it so annoying. Original recipients have the full list, but later additions to the thread don't know who the original recipients were, only that including the list in reply will also reach the original recipients (albeit maybe not filtered into the right folder). I have no idea if mailman has some tweakable setting that can change this bad out-of-the-box default of munging cc's that so many lists use, but even if it does, it requires a list admin to tweak the setting, for each affected list. This means I cannot send Please CC maintainer emails anymore because I cannot be sure whether the maintainer was CCed! Well, unless you know the maintainer is one of the people who does NOT use the mailman setting of don't send me duplicate mails (sadly, we have deduced that Kevin does use it, making it harder to tell if he is aware of a thread). Sorry, I wasn't aware about this behaviour. I thought I had finally found the one use case where this option actually makes sense, but it turns out that even if you really want the advertised thing, the option is useless crap. I've fixed my mailman settings and replicated the functionality I really want in additional email filter rules. Hope I got it right and emails that I should see won't be disappearing... Please let me know if you still see me removed from CC lists. Thanks! Stefan pgpQSDdwaQhqh.pgp Description: PGP signature
Re: [Qemu-block] [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open()
Am 09.06.2015 um 17:21 hat Eric Blake geschrieben: On 06/09/2015 08:48 AM, Stefan Hajnoczi wrote: I guess my @redhat.com email was received directly from Max because I was in CC list. It didn't pass through Mailman. I saw the original, unmodified list of CCs with Kevin included. The @gmail.com email was received from the mailing list. Mailman did what you described. And that's what makes it so annoying. Original recipients have the full list, but later additions to the thread don't know who the original recipients were, only that including the list in reply will also reach the original recipients (albeit maybe not filtered into the right folder). I have no idea if mailman has some tweakable setting that can change this bad out-of-the-box default of munging cc's that so many lists use, but even if it does, it requires a list admin to tweak the setting, for each affected list. This means I cannot send Please CC maintainer emails anymore because I cannot be sure whether the maintainer was CCed! Well, unless you know the maintainer is one of the people who does NOT use the mailman setting of don't send me duplicate mails (sadly, we have deduced that Kevin does use it, making it harder to tell if he is aware of a thread). Sorry, I wasn't aware about this behaviour. I thought I had finally found the one use case where this option actually makes sense, but it turns out that even if you really want the advertised thing, the option is useless crap. I've fixed my mailman settings and replicated the functionality I really want in additional email filter rules. Hope I got it right and emails that I should see won't be disappearing... Please let me know if you still see me removed from CC lists. Kevin pgp4oWLNlCKyr.pgp Description: PGP signature
Re: [Qemu-block] [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open()
On 06/09/2015 04:19 AM, Stefan Hajnoczi wrote: On Tue, Jun 09, 2015 at 10:59:42AM +0200, Kevin Wolf wrote: Am 09.06.2015 um 10:41 hat Stefan Hajnoczi geschrieben: On Thu, Mar 19, 2015 at 6:53 PM, Max Reitz mre...@redhat.com wrote: BDRV_O_PROTOCOL is an internal qemu flag which a user should be able to override by explicitly specifying a block driver. This series implements this and adds two iotests (one for NBD, one for file) to test it. Please resend and CC Kevin (for qemu-iotests and block.c). It's only you who dropped me from CC. :-) For sanity, can you check whether you are on the CC list in Max's second ping message: 556f5a4d.50...@redhat.com? I had another CC mix-up recently and want to check whether my mail tools are dropping CCs or if it's just me being confused. mailman has an (extremely annoying, in my opinion) habit of munging cc: lines to drop the name of any recipient who has set their list delivery options to avoid duplicate messages where the recipient is in cc. Ultimately, the end user still gets the messages (reply-to-all gets the message back to the list, even though it drops the cc), but at the expense of not directly going to the inbox as desired. At least I still only get one copy of the message, but yes, I'd rather have that one copy come directly to me for all messages in the thread, rather than through the list because I was munged out of cc. I hope that mailman3/hyperkitty will have saner defaults and not munge cc lists to exclude subscribers merely based on their preference on duplicate mail receipt. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: [Qemu-block] [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open()
On Tue, Jun 9, 2015 at 12:49 PM, Eric Blake ebl...@redhat.com wrote: On 06/09/2015 04:19 AM, Stefan Hajnoczi wrote: On Tue, Jun 09, 2015 at 10:59:42AM +0200, Kevin Wolf wrote: Am 09.06.2015 um 10:41 hat Stefan Hajnoczi geschrieben: On Thu, Mar 19, 2015 at 6:53 PM, Max Reitz mre...@redhat.com wrote: BDRV_O_PROTOCOL is an internal qemu flag which a user should be able to override by explicitly specifying a block driver. This series implements this and adds two iotests (one for NBD, one for file) to test it. Please resend and CC Kevin (for qemu-iotests and block.c). It's only you who dropped me from CC. :-) For sanity, can you check whether you are on the CC list in Max's second ping message: 556f5a4d.50...@redhat.com? I had another CC mix-up recently and want to check whether my mail tools are dropping CCs or if it's just me being confused. mailman has an (extremely annoying, in my opinion) habit of munging cc: lines to drop the name of any recipient who has set their list delivery options to avoid duplicate messages where the recipient is in cc. Ultimately, the end user still gets the messages (reply-to-all gets the message back to the list, even though it drops the cc), but at the expense of not directly going to the inbox as desired. At least I still only get one copy of the message, but yes, I'd rather have that one copy come directly to me for all messages in the thread, rather than through the list because I was munged out of cc. I hope that mailman3/hyperkitty will have saner defaults and not munge cc lists to exclude subscribers merely based on their preference on duplicate mail receipt. Wow! You are right: I checked my @redhat.com inbox and I see 556f5a4d.50...@redhat.com has Kevin in CC. I checked my @gmail.com inbox (subscribed to mailing list) and I see 556f5a4d.50...@redhat.com does not have Kevin in CC. I guess my @redhat.com email was received directly from Max because I was in CC list. It didn't pass through Mailman. I saw the original, unmodified list of CCs with Kevin included. The @gmail.com email was received from the mailing list. Mailman did what you described. This means I cannot send Please CC maintainer emails anymore because I cannot be sure whether the maintainer was CCed! Stefan
Re: [Qemu-block] [Qemu-devel] [PATCH v2 0/2] block: driver should override flags in bdrv_open()
On 06/09/2015 08:48 AM, Stefan Hajnoczi wrote: I guess my @redhat.com email was received directly from Max because I was in CC list. It didn't pass through Mailman. I saw the original, unmodified list of CCs with Kevin included. The @gmail.com email was received from the mailing list. Mailman did what you described. And that's what makes it so annoying. Original recipients have the full list, but later additions to the thread don't know who the original recipients were, only that including the list in reply will also reach the original recipients (albeit maybe not filtered into the right folder). I have no idea if mailman has some tweakable setting that can change this bad out-of-the-box default of munging cc's that so many lists use, but even if it does, it requires a list admin to tweak the setting, for each affected list. This means I cannot send Please CC maintainer emails anymore because I cannot be sure whether the maintainer was CCed! Well, unless you know the maintainer is one of the people who does NOT use the mailman setting of don't send me duplicate mails (sadly, we have deduced that Kevin does use it, making it harder to tell if he is aware of a thread). -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
