From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kees Cook <keescook@chromium.org>,
"tools@linux.kernel.org" <tools@linux.kernel.org>,
Kalle Valo <kvalo@kernel.org>
Subject: Re: b4 tag parsing too lax?
Date: Thu, 14 Sep 2023 09:44:21 -0400 [thread overview]
Message-ID: <20230914-overstuff-dreaded-70e1ae@meerkat> (raw)
In-Reply-To: <ff72f308879a12f53fa7ace044ab99ab7dd9e060.camel@sipsolutions.net>
On Thu, Sep 14, 2023 at 08:55:25AM +0200, Johannes Berg wrote:
> We use patchwork in wireless to assign the work between Kalle and I. I
> guess I could still apply patches using b4 though, but don't, at this
> point.
You can integrate b4 with patchwork, to a degree. At the very least, you can
pass patchwork URLs to `b4 am` and reasonably expect them to do the right
thing (as long as it's the version of patchwork that uses msgid URLs for
threads).
-K
next prev parent reply other threads:[~2023-09-14 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 19:44 b4 tag parsing too lax? Kees Cook
2023-09-13 20:00 ` Konstantin Ryabitsev
2023-09-13 23:04 ` Kees Cook
2023-09-14 6:55 ` Johannes Berg
2023-09-14 13:44 ` Konstantin Ryabitsev [this message]
2023-09-14 16:55 ` Kees Cook
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=20230914-overstuff-dreaded-70e1ae@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=keescook@chromium.org \
--cc=kvalo@kernel.org \
--cc=tools@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.