patch-hub is a terminal-based user interface (TUI) designed to simplify
working with software patches sent through mailing lists in Linux-related
development. It provides an efficient way to navigate and interact with patches
archived on lore.kernel.org, specifically for the
Linux kernel and adjacent projects.
patch-hub is a sub-project of kw, a Developer Automation Workflow System
(DAWS) for Linux kernel developers. The goal of kw is to "reduce the setup
overhead of working with the Linux kernel and provide tools to support
developers in their daily tasks."
While patch-hub can be used as a standalone tool, we highly recommend
integrating it with the full kw suite for a more seamless developer
experience. Check out the kw
repository to learn more.
-
Mailing List Selection — Dynamically fetch and browse mailing lists archived on lore.kernel.org.
-
Latest Patchsets — View the most recent patchsets from a selected mailing list in an organized flow.
-
Patchset Details & Actions — View individual patch contents and access metadata like title, author, version, number of patches, last update, and code-review trailers. Take quick actions like:
- Apply patch(set) to your local kernel tree.
- Bookmark important patches
- Reply with
Reviewed-bytags to the series.
-
Bookmarking System — Bookmark patchsets for easy reference later.
-
Enhanced Patchset Rendering — Use external tools such as
bat,delta,diff-so-fancyfor better visualization or use the built-in vanilla renderer (default) for a dependency-free experience.
Future updates will introduce deeper integration with kw, including:
- Seamlessly compile and deploy patchset versions of the kernel to target machines.
Before using patch-hub, make sure you have the following packages installed:
b4- Required for working with patches from mailing lists.git-email- Provides thegit send-emailcommand for replying to patches.- Optional (but recommended) patchset renderers for enhanced previews:
patch-hub is a part of kw so if you already use kw, you don’t need to
install Patch Hub separately—simply update kw to the latest version:
kw self-update After updating kw, you can launch patch-hub using:
kw patch-hubIf you’re not using kw yet, consider installing it for a
more fluid experience with patch-hub and other useful tools included in kw.
Download pre-compiled binaries from our releases page.
We provide two versions:
-x86_64-unknown-linux-gnu– Dynamically linked, relies on the GNU C Library (glibc), making it more compatible across Linux distributions.-x86_64-unknown-linux-musl– Statically linked, built with musl libc, producing a more portable and self-contained binary.
📌 Requirements: Ensure Rust (rustc) and Cargo are
installed on your system.
To build patch-hub from source:
1️⃣ Clone the repository: bash git clone https://github.com/kworkflow/patch-hub.git && cd patch-hub
2️⃣ Compile
with Cargo: bash cargo build --release
3️⃣ The compiled binary will be available at:
target/release/patch-hubtarget/debug/patch-hub(default build, without the--releaseoption)
Additionally, you can install the binary to make it available anywhere on your
system: bash cargo install --path .
We appreciate all contributions, whether it’s fixing bugs, adding features, improving documentation, or suggesting ideas! If you're looking for something to work on, check out our issues page.
Since patch-hub is a sub-project of kw, some development workflows carry over — such as a similar branching strategy (master and unstable) — but keep in mind that patch-hub is written in Rust, while kw is Bash. For detailed guidelines on setting up your environment, coding standards, and submitting Pull Requests, please refer to our CONTRIBUTING.md.
- Report Issues: Found a bug or have a feature request? Open an issue here.
- Submit a PR: Fix an issue, improve code, or add a new feature—just follow the steps in CONTRIBUTING.md.
- Improve Documentation: Enhancements to the README, guides, and comments are always welcome!