From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: workflows@vger.kernel.org
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: Is there an integrated b4 + patchwork guide for maintainers?
Date: Thu, 11 Sep 2025 16:54:32 -0700 [thread overview]
Message-ID: <972dd368-282a-4255-9b88-6324c1924512@oss.qualcomm.com> (raw)
In-Reply-To: <1bcfbc51-18bb-4a5c-8a1e-a2de794ff00f@quicinc.com>
On 7/17/2024 12:30 PM, Jeff Johnson wrote:
> I'm in the process of taking over ath.git maintainer activities from Kalle. He
> has shared his workflow, but much of it is based upon using Stacked Git (STG)
> and a patchwork script he authored. I seems like many (most?) maintainers are
> now using b4, and Kalle fully supports me using it, so I just want to see if
> there is a guide or sample workflow for using b4 along with patchwork. I'd
> like to adopt a proven workflow rather than stumbling around on my own.
I sent this over a year ago (using my former credentials). I did not receive
any responses at that time, so I just cobbled things together.
In light of current discussion about using Link: tags, and related discussion
about how multi-commit series should be treated (applied linearly or merged
from a dev branch), it seems timely to re-ask the question. Is there a guide
or recommended sample workflow for using b4 along with patchwork?
/jeff
next prev parent reply other threads:[~2025-09-11 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 19:30 Jeff Johnson
2025-09-11 23:54 ` Jeff Johnson [this message]
2025-09-12 1:22 ` dan.j.williams
2025-09-14 12:44 ` Krzysztof Kozlowski
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=972dd368-282a-4255-9b88-6324c1924512@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=konstantin@linuxfoundation.org \
--cc=workflows@vger.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