b4 picking the wrong message

b4 picking the wrong message

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

Hi Konstantin,

When I ask b4 am to fetch either of these message IDs:

   20200626164623.87894-1-sebastian.reichel@collabora.com
   DB6PR1001MB10965E5BDA9B3EF570B607A4806A0@DB6PR1001MB1096.EURPRD10.PROD.OUTLOOK.COM

both of which are for v4 of a single patch that was previously part of a
series b4 fetches v3 of that series rather than the v4 I thought I was
asking for. I see that the patch (the first message ID) was sent in
reply to discussion of v3 of the series which is probably confusing
things, there's also the use of PATCHv4 rather than PATCH v4.

Thanks,
Mark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

Re: b4 picking the wrong message

[Konstantin Ryabitsev]

On Fri, Jul 03, 2020 at 07:52:37PM +0100, Mark Brown wrote:
> Hi Konstantin,
> 
> When I ask b4 am to fetch either of these message IDs:
> 
>    20200626164623.87894-1-sebastian.reichel@collabora.com
>    DB6PR1001MB10965E5BDA9B3EF570B607A4806A0@DB6PR1001MB1096.EURPRD10.PROD.OUTLOOK.COM
> 
> both of which are for v4 of a single patch that was previously part of a
> series b4 fetches v3 of that series rather than the v4 I thought I was
> asking for. I see that the patch (the first message ID) was sent in
> reply to discussion of v3 of the series which is probably confusing
> things, there's also the use of PATCHv4 rather than PATCH v4.

That's the culprit -- we look for a standalone word "PATCH" inside the 
brackets, so if it's mangled as [PATCHv4], then we don't consider that 
message. I added logic to master/stable-0.5.y to deal with that case.

Thanks,
-K

Re: b4 picking the wrong message

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 320 bytes --]

On Mon, Jul 06, 2020 at 06:11:36PM -0400, Konstantin Ryabitsev wrote:

> That's the culprit -- we look for a standalone word "PATCH" inside the 
> brackets, so if it's mangled as [PATCHv4], then we don't consider that 
> message. I added logic to master/stable-0.5.y to deal with that case.

That worked, thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 499 bytes --]