From: Maurice Hieronymus <mhi@mailbox.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>, tools@kernel.org
Cc: Maurice Hieronymus <mhi@mailbox.org>
Subject: RFC: b4 prep --enforce-deps to materialize series dependencies locally
Date: Sat, 11 Jul 2026 10:19:37 +0200 [thread overview]
Message-ID: <20260711081938.59972-1-mhi@mailbox.org> (raw)
Hi Konstantin,
b4 prep can declare series dependencies (--edit-deps) and verify them
(--check-deps), but it never materializes them: --check-deps applies
everything in a throwaway sparse worktree and discards it. If I work
on stacked series, I still stack the branches by hand, and re-stack
them by hand every time a prerequisite gets a new revision.
I'd like to close that gap with something like:
b4 prep --enforce-deps
which reads the declared prerequisites, figures out what needs to be
rebased on what, and runs the git commands to bring the local branch
into the state the dependencies describe. Conflicts stop the rebase
as usual and are the user's problem. Since an enforce can involve
several steps, there would also be:
b4 prep --abort-enforce-deps
which restores the pre-enforce state after a partially completed
enforce. That means saving the branch head and tracking state to
a backup ref before touching anything.
If this is seen as useful I can sketch a prototype and send patches.
Best,
Maurice
reply other threads:[~2026-07-11 8:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260711081938.59972-1-mhi@mailbox.org \
--to=mhi@mailbox.org \
--cc=konstantin@linuxfoundation.org \
--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