From: Konstantin Ryabitsev <mricon@kernel.org>
To: ksummit@lists.linux.dev
Subject: [TECH TOPIC] new maintainer-oriented features of b4
Date: Thu, 2 Apr 2026 00:15:47 -0400 [thread overview]
Message-ID: <20260402-singing-silver-swine-c7e31b@lemur> (raw)
Hello, all:
I would like to propose a tech topic for the upcoming kernel summit.
B4 is already a well-known tool for retrieving and applying series from
lore.kernel.org. Recently, it gained several new features that can make the
life of a maintainer a bit easier:
- b4 review - helps with code review and full series lifecycle management
- b4 bugs - integrates distributed bug tracking into your workflow
This session will go over the new features and how they can assist overloaded
maintainers in keeping a handle on the stream of incoming changes and bug
reports while retaining decentralized nature of Linux kernel development.
Best regards,
--
KR
reply other threads:[~2026-04-02 4:15 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=20260402-singing-silver-swine-c7e31b@lemur \
--to=mricon@kernel.org \
--cc=ksummit@lists.linux.dev \
/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