Re: [PATCH v3 0/2] qemu-img: map: implement support for compressed clusters

[Kevin Wolf]

Am 22.09.2023 um 12:10 hat Kevin Wolf geschrieben:
> Am 21.09.2023 um 19:02 hat Andrey Drobyshev geschrieben:
> > On 9/14/23 16:34, Kevin Wolf wrote:
> > > Am 07.09.2023 um 23:02 hat Andrey Drobyshev via geschrieben:
> > >> v2 --> v3:
> > >>   * Make "compressed" field mandatory, not optional;
> > >>   * Adjust field description in qapi/block-core.json;
> > >>   * Squash patch 3 into patch 2 so that failing tests don't break bisect;
> > >>   * Update even more tests' outputs now that the field is mandatory.
> > >>
> > >> v2: 
> > >> https://lists.nongnu.org/archive/html/qemu-block/2023-07/msg00106.html
> > > 
> > > Thanks, applied to the block branch.
> > > 
> > > Kevin
> > > 
> > 
> > Hi Kevin,
> > 
> > In the patches applied to master something went wrong and my email isn't
> > displayed correctly:
> > 
> > > commit 2848289168fbbd9a6855c84ec8fde8929a2b042b
> > > Author: Andrey Drobyshev via <qemu-block@nongnu.org>   <--------
> > > Date:   Fri Sep 8 00:02:25 2023 +0300
> > > 
> > >     block: add BDRV_BLOCK_COMPRESSED flag for bdrv_block_status()
> > 
> > > commit 52b10c9c0c68e90f9503ba578f2eaf8975c1977f        
> > > Author: Andrey Drobyshev via <qemu-block@nongnu.org>   <--------
> > > Date:   Fri Sep 8 00:02:26 2023 +0300
> > > 
> > >     qemu-img: map: report compressed data blocks
> > 
> > There's probably no way to fix that in master, but just giving you a
> > heads-up for maybe there's a bug in your scripts.
> 
> Yes, too late to fix it in master. I would have to notice this earlier
> and then fix it manually.
> 
> But it's not a bug on my side (I'm only using 'git am' anyway), this is
> actually how the email is sent by Mailman:
> 
> From: Andrey Drobyshev via <qemu-devel@nongnu.org>
> 
> You can see the same problem in Patchew:
> 
> 20230919165804.439110-1-andrey.drobyshev@virtuozzo.com/">https://patchew.org/QEMU/20230919165804.439110-1-andrey.drobyshev@virtuozzo.com/
> 
> If I understand correctly, the problem is with the DMARC policy of
> virtuozzo.com, which forces the mailing list to rewrite the From: header
> in order to avoid being treated as spam:
> 
> https://wiki.list.org/DEV/DMARC
> 
> I don't know why it happens only on some of your emails, though.

Actually, part of the issue is on my side and I think it is what causes
the inconsistenty, but I don't really have any influence on it.

If you check Patchew, you'll see that your name is consistently mangled
there. What saves you in most cases is that you CC me directly and
therefore Mailman isn't even involved.

However, GMail (which is used by redhat.com) has this terrible idea that
it can "deduplicate" emails that look similar enough, so whatever
arrives first is what I get to see and the other copy is thrown away. So
this must have been a case where the mailing list copy was delivered
faster than your original one.

The only thing I could theoretically do to improve the situation a bit
is switching to a more reasonable email provider for upstream work. So
far the differences between GMail and real email haven't been a big
enough problem to be worth the hassle, though.

Kevin