From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Paul Moore <paul@paul-moore.com>, Chuck Lever <chucklever@gmail.com>
Cc: 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 17:51:18 +0100 [thread overview]
Message-ID: <87v7euo0vt.fsf@toke.dk> (raw)
In-Reply-To: <CAHC9VhS7nBWxZ0=1c_ec=Lq+J0CqZUGbriu2i==X7FciSw0K2g@mail.gmail.com>
Paul Moore <paul@paul-moore.com> writes:
> On Tue, Mar 17, 2026 at 11:08 AM Chuck Lever <chucklever@gmail.com> wrote:
>>
>> Hi Konstantin -
>>
>> I'm a long-time Stacked Git and b4 user and I'm hunting for a tool to
>> juggle the many data items involved with posting kernel patch series
>> for review. "b4 prep" seems to fit that bill but it has some issues
>> when it comes to large cover letters with Stacked Git.
>>
>> The branch-description strategy is the least-bad option for StGit
>> right now, but it's fighting git's design -- git config was never
>> meant to hold multi-paragraph prose, and there's no way to tell StGit
>> "don't print the branch description in stg branch --list."
>>
>> 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.
And here! I have been using the "cover letter as commit" mode of b4,
which works as long as you remember to 'stg commit --all' before you
invoke b4. I requested a pre-hook functionality in b4 to automate this,
so will take this opportunity to bump that:
https://lore.kernel.org/tools/87ttdkrylx.fsf@toke.dk/
-Toke
next prev parent reply other threads:[~2026-03-17 16:58 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
2026-03-17 16:51 ` Toke Høiland-Jørgensen [this message]
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=87v7euo0vt.fsf@toke.dk \
--to=toke@toke.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.