From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: submitting-patches: Advertise b4
Date: Wed, 4 Sep 2024 04:44:51 +0200 [thread overview]
Message-ID: <20240904044443.309aabb1@foz.lan> (raw)
In-Reply-To: <20240903-documentation-b4-advert-v1-1-c89d6f5db7b1@kernel.org>
Em Tue, 03 Sep 2024 23:42:04 +0100
Mark Brown <broonie@kernel.org> escreveu:
> b4 is now widely used and is quite helpful for a lot of the things that
> submitting-patches covers, let's advertise it to submitters to try to make
> their lives easier and reduce the number of procedural issues maintainers
> see.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Documentation/process/submitting-patches.rst | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index f310f2f36666..4b6904184ad1 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -842,6 +842,16 @@ Make sure that base commit is in an official maintainer/mainline tree
> and not in some internal, accessible only to you tree - otherwise it
> would be worthless.
>
> +
> +Tooling
> +-------
> +
> +Many of the technical aspects of this process can be automated using
> +b4, documented at <https://b4.docs.kernel.org/en/latest/>. This can
> +help with things like tracking dependencies, running checkpatch and
> +with formatting and sending mails.
> +
> +
No need for two blank lines (yeah, there's a mix on this file of using
one or two blank lines for paragraphs).
I would also add quick example(s) on how to use it for common workflows.
> References
> ----------
>
>
> ---
> base-commit: 7c626ce4bae1ac14f60076d00eafe71af30450ba
> change-id: 20240903-documentation-b4-advert-18016e83d7d9
>
> Best regards,
Thanks,
Mauro
next prev parent reply other threads:[~2024-09-04 2:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 22:42 Mark Brown
2024-09-04 2:44 ` Mauro Carvalho Chehab [this message]
2024-09-04 11:30 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2024-09-03 22:38 Mark Brown
2024-09-03 22:36 Mark Brown
2024-09-03 23:06 ` Shuah Khan
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=20240904044443.309aabb1@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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