All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vernet <void@manifault.com>
To: konstantin@linuxfoundation.org
Cc: users@linux.kernel.org, tools@linux.kernel.org,
	void@manifault.com, kernel-team@fb.com
Subject: [PATCH 2/2] man: Update man page to use bold where appropriate
Date: Fri, 18 Feb 2022 07:31:28 -0800	[thread overview]
Message-ID: <20220218153128.914071-2-void@manifault.com> (raw)
In-Reply-To: <20220218153128.914071-1-void@manifault.com>

According to https://man7.org/linux/man-pages/man1/man.1.html, when writing
a man page for a program, anything that should be typed exactly as shown
should use bolded text. The b4 man page has a SUBCOMMANDS section where
subcommands are listed as 'b4 <subcommand>', in italics. So as to match the
guidance for man pages (as well as to match the examples provided at the
link above), this diff updates the 'b4' portion of the aforementioned
subcommand section to be bolded.

Signed-off-by: David Vernet <void@manifault.com>
---
 man/b4.5.rst | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/man/b4.5.rst b/man/b4.5.rst
index ab12804..b45909a 100644
--- a/man/b4.5.rst
+++ b/man/b4.5.rst
@@ -27,14 +27,14 @@ precursor to Lore and Data in the Star Trek universe.
 
 SUBCOMMANDS
 -----------
-* *b4 mbox*: Download a thread as an mbox file
-* *b4 am*: Create an mbox file that is ready to git-am
-* *b4 shazam*: Similar to *am*, but lets you apply patches directly
-* *b4 pr*: Work with pull requests
-* *b4 diff*: Show range-diff style diffs between patch versions
-* *b4 ty*: Create templated replies for processed patches and pull requests
-* *b4 attest*: (EXPERIMENTAL) Add cryptographic attestation to patches
-* *b4 kr* (EXPERIMENTAL) Operate on patatt-compatible keyrings
+* **b4** *mbox*: Download a thread as an mbox file
+* **b4** *am*: Create an mbox file that is ready to git-am
+* **b4** *shazam*: Similar to *am*, but lets you apply patches directly
+* **b4** *pr*: Work with pull requests
+* **b4** *diff*: Show range-diff style diffs between patch versions
+* **b4** *ty*: Create templated replies for processed patches and pull requests
+* **b4** *attest*: (EXPERIMENTAL) Add cryptographic attestation to patches
+* **b4** *kr* (EXPERIMENTAL) Operate on patatt-compatible keyrings
 
 OPTIONS
 -------
-- 
2.30.2


      reply	other threads:[~2022-02-18 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 21:08 [PATCH 1/2] man: Update man page to mention HTTPS_PROXY David Vernet
2022-01-18 21:08 ` [PATCH 2/2] man: Update man page to use bold where appropriate David Vernet
2022-02-18 15:31 ` [PATCH 1/2] man: Update man page to mention HTTPS_PROXY David Vernet
2022-02-18 15:31   ` David Vernet [this message]

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=20220218153128.914071-2-void@manifault.com \
    --to=void@manifault.com \
    --cc=kernel-team@fb.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@linux.kernel.org \
    --cc=users@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.