From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Chuck Lever <chucklever@gmail.com>,
Konstantin Ryabitsev <mricon@kernel.org>,
users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: Using "b4 prep" with Stacked Git
Date: Tue, 17 Mar 2026 16:54:52 +0100 [thread overview]
Message-ID: <87tsuecuyb.fsf@bootlin.com> (raw)
In-Reply-To: <CAHC9VhS7nBWxZ0=1c_ec=Lq+J0CqZUGbriu2i==X7FciSw0K2g@mail.gmail.com> (Paul Moore's message of "Tue, 17 Mar 2026 11:26:54 -0400")
Hello,
>> A file-based strategy would solve all three problems cleanly. Something like:
>>
>> .git/b4-cover/<branchname>/subject
>> .git/b4-cover/<branchname>/body
>> .git/b4-cover/<branchname>/changelog
>> .git/b4-cover/<branchname>/recipients
>
> Fellow stacked git fan here.
>
> I do something very similar with my own scripts/tools, and if I could
> offer a suggestion based on my experience, you might want to consider
> some slight naming tweaks to support multiple cover letters in a
> single branch.
I've transitioned to b4 a few months ago, I really like the tool, but if
there is one key feature it lacks based on my very own workflow, it is
indeed the capability to stack series. I often have to manage several
series which depend on each other. b4 in this case requires one branch
per series which is painful to maintain.
A big +1 to whoever will propose such a stacked Git capability :-)
Cheers,
Miquèl
next prev parent reply other threads:[~2026-03-17 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 15:01 Using "b4 prep" with Stacked Git Chuck Lever
2026-03-17 15:26 ` Paul Moore
2026-03-17 15:48 ` Chuck Lever
2026-03-17 18:57 ` Paul Moore
2026-03-17 15:54 ` Miquel Raynal [this message]
2026-03-17 16:51 ` Toke Høiland-Jørgensen
2026-03-17 17:45 ` Chuck Lever
2026-03-18 14:44 ` Toke Høiland-Jørgensen
2026-03-20 16:25 ` Konstantin Ryabitsev
2026-03-21 20:53 ` Toke Høiland-Jørgensen
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=87tsuecuyb.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=chucklever@gmail.com \
--cc=mricon@kernel.org \
--cc=paul@paul-moore.com \
--cc=tools@linux.kernel.org \
--cc=users@linux.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