b4 send patch order

b4 send patch order

[Ira Weiny]

Konstantin,

When using 'b4 send' what sets the 'Date: ' tag in the emails?

Dan and I discovered that this thread:

https://lore.kernel.org/all/20221221-ira-cxl-events-2022-11-17-v2-0-2ce2ecc06219@intel.com/

Seems to have a 0/8 email which is dated many seconds after 1/8.

	20:24:53 vs 20:24:31

This messed with how notmuch mail displays this thread as it uses the Date in
the emails for display order.

All the headers I see indicate that 0/8 arrived before 1/8.[*]  So it looks
like b4 is sending these in order.  I'm trying to understand this better.
I would blame the exchange server here at Intel if not for the emails
apparently coming to vger in order?

	20:25:19 vs 23:25:20

:-/

Thanks,
Ira


[*]

0/8: (https://lore.kernel.org/all/20221221-ira-cxl-events-2022-11-17-v2-0-2ce2ecc06219@intel.com/raw)

...
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S231146AbiLVEZT (ORCPT <rfc822;linux-cxl@archiver.kernel.org>);
	        Wed, 21 Dec 2022 23:25:19 -0500
...
Date:   Wed, 21 Dec 2022 20:24:53 -0800
...


1/8: (https://lore.kernel.org/all/20221221-ira-cxl-events-2022-11-17-v2-1-2ce2ecc06219@intel.com/raw)

...
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S229742AbiLVEZU (ORCPT <rfc822;linux-cxl@archiver.kernel.org>);
	        Wed, 21 Dec 2022 23:25:20 -0500
...
Date:   Wed, 21 Dec 2022 20:24:31 -0800

Re: b4 send patch order

[Konstantin Ryabitsev]

On Tue, Jan 17, 2023 at 07:40:39PM -0800, Ira Weiny wrote:
> Konstantin,
> 
> When using 'b4 send' what sets the 'Date: ' tag in the emails?
> 
> Dan and I discovered that this thread:
> 
> https://lore.kernel.org/all/20221221-ira-cxl-events-2022-11-17-v2-0-2ce2ecc06219@intel.com/
> 
> Seems to have a 0/8 email which is dated many seconds after 1/8.
> 
> 	20:24:53 vs 20:24:31

I don't actually know how this happened. I did find a small bug in how we do
this, but it caused the cover letter to have the same Date as the first patch,
when the intent is to have every consecutive message in the series to
increment by 1 second.

Even in the 0.11.0 version that was used to send that series, the Date: header
was generated using the same "series timestamp", so I don't have an
explanation how the Date: header in the cover letter was so many seconds after
the first patch.

- https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/b4/ez.py?h=v0.11.0#n1118
- https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/b4/ez.py?h=v0.11.0#n1135
- https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/b4/ez.py?h=v0.11.0#n1178
- https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/b4/ez.py?h=v0.11.0#n1012

So, it's a mystery, unfortunately!

-K

Re: b4 send patch order

[Ira Weiny]

Konstantin Ryabitsev wrote:
> On Tue, Jan 17, 2023 at 07:40:39PM -0800, Ira Weiny wrote:
> > Konstantin,
> > 
> > When using 'b4 send' what sets the 'Date: ' tag in the emails?
> > 
> > Dan and I discovered that this thread:
> > 
> > https://lore.kernel.org/all/20221221-ira-cxl-events-2022-11-17-v2-0-2ce2ecc06219@intel.com/
> > 
> > Seems to have a 0/8 email which is dated many seconds after 1/8.
> > 
> > 	20:24:53 vs 20:24:31
> 
> I don't actually know how this happened. I did find a small bug in how we do
> this, but it caused the cover letter to have the same Date as the first patch,
> when the intent is to have every consecutive message in the series to
> increment by 1 second.
> 
> Even in the 0.11.0 version that was used to send that series, the Date: header
> was generated using the same "series timestamp", so I don't have an
> explanation how the Date: header in the cover letter was so many seconds after
> the first patch.
> 
> - https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/b4/ez.py?h=v0.11.0#n1118
> - https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/b4/ez.py?h=v0.11.0#n1135
> - https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/b4/ez.py?h=v0.11.0#n1178
> - https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/b4/ez.py?h=v0.11.0#n1012
> 
> So, it's a mystery, unfortunately!

:-/

Well ok thanks for looking.  It only appears to be that thread.  Others I
have sent seem to be fine.

For those following along though notmuch mail can order by message id.
(SORT_MESSAGE_ID) The man page did not list this but Dan found it in the
code.

So in notmuch.vim you can use:

+               q.sort = Notmuch::SORT_MESSAGE_ID

Thanks for looking!  :-D
Ira