From: "Michael S. Tsirkin" <mst@redhat.com>
To: tools@kernel.org
Subject: [PATCH 0/2] b4: sparse-checkout related fixes
Date: Mon, 13 Oct 2025 18:20:04 -0400 [thread overview]
Message-ID: <cover.1760393880.git.mst@redhat.com> (raw)
I encountered shazam test failures, diagnozing them I realized
b4 misuses the sparse-checkout command.
This patchset cleans this up.
Pls review, thanks!
Michael S. Tsirkin (2):
test_shazam: clean worktree before git am
ez: cleanup sparse-checkout usage
src/b4/__init__.py | 6 +++---
src/b4/ez.py | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
--
MST
next reply other threads:[~2025-10-13 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 22:20 Michael S. Tsirkin [this message]
2025-10-13 22:20 ` [PATCH 1/2] test_shazam: clean worktree before git am Michael S. Tsirkin
2025-10-13 22:20 ` [PATCH 2/2] ez: cleanup sparse-checkout usage Michael S. Tsirkin
2025-10-15 21:07 ` [PATCH 0/2] b4: sparse-checkout related fixes Michael S. Tsirkin
2025-10-17 0:08 ` Konstantin Ryabitsev
2025-10-22 17:35 ` Konstantin Ryabitsev
2025-10-22 19:57 ` Konstantin Ryabitsev
2025-10-22 19:58 ` Konstantin Ryabitsev
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=cover.1760393880.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=tools@kernel.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 NNTP newsgroup(s).