workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: <workflows@vger.kernel.org>
Subject: Is there an integrated b4 + patchwork guide for maintainers?
Date: Wed, 17 Jul 2024 12:30:15 -0700	[thread overview]
Message-ID: <1bcfbc51-18bb-4a5c-8a1e-a2de794ff00f@quicinc.com> (raw)

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.

/jeff

             reply	other threads:[~2024-07-17 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 19:30 Jeff Johnson [this message]
2025-09-11 23:54 ` Jeff Johnson
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=1bcfbc51-18bb-4a5c-8a1e-a2de794ff00f@quicinc.com \
    --to=quic_jjohnson@quicinc.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