From: Ira Weiny <ira.weiny@intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Ira Weiny <ira.weiny@intel.com>
Cc: <tools@linux.kernel.org>, Dan Williams <dan.j.williams@intel.com>,
"Vishal Verma" <vishal.l.verma@intel.com>
Subject: Re: b4 send patch order
Date: Thu, 19 Jan 2023 13:39:41 -0800 [thread overview]
Message-ID: <63c9b89de923b_af27e294b5@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20230119174805.zz3urz5gfwj6mkre@meerkat.local>
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
prev parent reply other threads:[~2023-01-19 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 3:40 b4 send patch order Ira Weiny
2023-01-19 17:48 ` Konstantin Ryabitsev
2023-01-19 21:39 ` Ira Weiny [this message]
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=63c9b89de923b_af27e294b5@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=dan.j.williams@intel.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@linux.kernel.org \
--cc=vishal.l.verma@intel.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).