From: Ira Weiny <ira.weiny@intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
<tools@linux.kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>
Subject: b4 send patch order
Date: Tue, 17 Jan 2023 19:40:39 -0800 [thread overview]
Message-ID: <Y8dqN1DgZ6Fwbk6H@iweiny-desk3> (raw)
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
next reply other threads:[~2023-01-18 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 3:40 Ira Weiny [this message]
2023-01-19 17:48 ` b4 send patch order Konstantin Ryabitsev
2023-01-19 21:39 ` Ira Weiny
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=Y8dqN1DgZ6Fwbk6H@iweiny-desk3 \
--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