From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: git@vger.kernel.org
Subject: b4 new contributor-oriented features
Date: Mon, 19 Sep 2022 10:54:45 -0400 [thread overview]
Message-ID: <20220919145445.ifpjcah44pql2erl@meerkat.local> (raw)
Hi, all:
If you submit patches to git, I would like to invite you to try out b4's new
contributor-oriented features:
* b4 prep: allows to get your patch series ready for sending to the maintainer
for review
* b4 send: simplifies the process of submitting your patches to the git
mailing list -- even if you don’t have access to a compliant SMTP server
* b4 trailers: simplifies the process of retrieving code-review trailers
received on the distribution lists and applying them to your tree
You can view this process as an alternative to GitHub PR + GitGitGadget
(sans all the nice CI features, just the actual submission). You can read full
documentation about this workflow here:
https://b4.docs.kernel.org/en/stable-0.10.y/contributor/overview.html
Note: These features are very new, experimental, and likely contain bugs. I
would be happy to receive any problem reports or other feedback.
Best regards,
Konstantin Ryabitsev
reply other threads:[~2022-09-19 14:54 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=20220919145445.ifpjcah44pql2erl@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).