From: Mark Brown <broonie@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@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 12:30:28 +0100 [thread overview]
Message-ID: <bbe54c4e-dd0c-488c-bffd-f9dddf6b13f8@sirena.org.uk> (raw)
In-Reply-To: <20240904044443.309aabb1@foz.lan>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On Wed, Sep 04, 2024 at 04:44:51AM +0200, Mauro Carvalho Chehab wrote:
> Mark Brown <broonie@kernel.org> escreveu:
> > +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 have to say that the double lines between sections do help with
native readability of the document.
> I would also add quick example(s) on how to use it for common workflows.
The b4 documentation is already pretty good and the submitter side is
focused on a single task so it's much easier for people to navigate
than something like git where there's a lot of flexibility, I'm not sure
rewriting an abbreviated version is a great idea. Someone with a better
idea of what would be useful could always follow up and add that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-09-04 11:30 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
2024-09-04 11:30 ` Mark Brown [this message]
-- 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=bbe54c4e-dd0c-488c-bffd-f9dddf6b13f8@sirena.org.uk \
--to=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@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