From: Jacob Keller <jacob.e.keller@intel.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: <meta@public-inbox.org>
Subject: Re: downloading t.mbox.gz messages are not sorted in expected order
Date: Fri, 12 Apr 2024 16:59:35 -0700 [thread overview]
Message-ID: <c3faf176-bb37-48bf-8425-6f2face5ee6d@intel.com> (raw)
In-Reply-To: <20240411-dancing-pink-marmoset-f442d0@meerkat>
On 4/11/2024 3:42 PM, Konstantin Ryabitsev wrote:
> On Thu, Apr 11, 2024 at 03:32:43PM -0700, Jacob Keller wrote:
>> I sometimes download patch series off of public inbox hosted servers to
>> apply with git-am. Occasionally I have found that these do not apply
>> cleanly because the thread is not sorted in patch order.
>
> It's more than just the order -- if there are replies in the thread, the mbox
> file won't apply either.
>
If the order was correct, it is usually easy enough to just "git am
--skip" the patches which have no content. However...
> This is the reason why the b4 tool exists:
> https://b4.docs.kernel.org/
>
This is extremely useful and I was unaware of its existence. Thanks!!
>> For an example, see
>> https://lore.kernel.org/lkml/20240308230557.805580-1-alex.williamson@redhat.com/
>
> $ b4 am -o/tmp https://lore.kernel.org/lkml/20240308230557.805580-1-alex.williamson@redhat.com/
> Grabbing thread from lore.kernel.org/all/20240308230557.805580-1-alex.williamson@redhat.com/t.mbox.gz
> Analyzing 20 messages in the thread
> Looking for additional code-review trailers on lore.kernel.org
> Checking attestation on all messages, may take a moment...
> ---
> ✓ [PATCH v2 1/7] vfio/pci: Disable auto-enable of exclusive INTx IRQ
> ✓ [PATCH v2 2/7] vfio/pci: Lock external INTx masking ops
> + Reviewed-by: Eric Auger <eric.auger@redhat.com> (✓ DKIM/redhat.com)
> ✓ [PATCH v2 3/7] vfio: Introduce interface to flush virqfd inject workqueue
> + Reviewed-by: Eric Auger <eric.auger@redhat.com> (✓ DKIM/redhat.com)
> ✓ [PATCH v2 4/7] vfio/pci: Create persistent INTx handler
> + Reviewed-by: Eric Auger <eric.auger@redhat.com> (✓ DKIM/redhat.com)
> ✓ [PATCH v2 5/7] vfio/platform: Disable virqfds on cleanup
> + Reviewed-by: Kevin Tian <kevin.tian@intel.com> (✓ DKIM/intel.com)
> + Reviewed-by: Eric Auger <eric.auger@redhat.com> (✓ DKIM/redhat.com)
> ✓ [PATCH v2 6/7] vfio/platform: Create persistent IRQ handlers
> + Reviewed-by: Kevin Tian <kevin.tian@intel.com> (✓ DKIM/intel.com)
> + Reviewed-by: Eric Auger <eric.auger@redhat.com> (✓ DKIM/redhat.com)
> + Tested-by: Eric Auger <eric.auger@redhat.com> (✓ DKIM/redhat.com)
> ✓ [PATCH v2 7/7] vfio/fsl-mc: Block calling interrupt handler without trigger
> + Reviewed-by: Kevin Tian <kevin.tian@intel.com> (✓ DKIM/intel.com)
> + Reviewed-by: Eric Auger <eric.auger@redhat.com> (✓ DKIM/redhat.com)
> ---
> ✓ Signed: DKIM/redhat.com
> ---
> Total patches: 7
> ---
> Cover: /tmp/v2_20240308_alex_williamson_vfio_interrupt_eventfd_hardening.cover
> Link: https://lore.kernel.org/r/20240308230557.805580-1-alex.williamson@redhat.com
> Base: not specified
> git am /tmp/v2_20240308_alex_williamson_vfio_interrupt_eventfd_hardening.mbx
>
> -K
next prev parent reply other threads:[~2024-04-12 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 22:32 downloading t.mbox.gz messages are not sorted in expected order Jacob Keller
2024-04-11 22:42 ` Konstantin Ryabitsev
2024-04-12 23:59 ` Jacob Keller [this message]
2024-04-13 7:58 ` Eric Wong
2024-04-15 21:06 ` Jacob Keller
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3faf176-bb37-48bf-8425-6f2face5ee6d@intel.com \
--to=jacob.e.keller@intel.com \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.org \
/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).