All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Marzinski <bmarzins@redhat.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Martin Wilck <mwilck@suse.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>,
	DM_DEVEL-ML <dm-devel@lists.linux.dev>
Subject: Re: [PATCH 01/13] multipath-tools: multipathd.8.in: fix mandoc WARNINGs
Date: Thu, 19 Nov 2026 12:38:26 -0500	[thread overview]
Message-ID: <av80EsBawOfxfHXK@redhat.com> (raw)
In-Reply-To: <ac29a29d-9932-495a-b75f-1fe4fe7948c7@gmail.com>

On Wed, Nov 18, 2026 at 04:02:58PM +0100, Xose Vazquez Perez wrote:
> On 11/16/26 10:38 PM, Benjamin Marzinski wrote:
> 
> > On Fri, Nov 13, 2026 at 01:55:33PM +0100, Xose Vazquez Perez wrote:
> 
> > > @@ -77,7 +77,7 @@ multipathd executes the given command (see \fBCOMMANDS\fR below). If the
> > >   command contains whitespace or shell special characters, it needs to be quoted
> > >   like in \fImultipathd -k'show topology'\fR. No whitespace is allowed between
> > >   the \fB-k\fR and the command string.
> > > -
> > > +.br
> 
> > Nitpick: If we don't want an actual blank line in the option
> > description, I'm not sure the line break really matters here.
> My intention was simply to replace the blank line that mandoc was
> complaining about and remove the visible empty line while keeping the
> rest of the formatting as is.
> 
> That said, if you prefer merging it into a single continuous paragraph,
> I have no objection to dropping the .br in v2.

IMO, it's not worth doing a v2 just for this. But if you are already, then I
think dropping the .br makes sense.

-Ben


  reply	other threads:[~2026-11-19 17:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 12:55 [PATCH 00/13] multipath-tools: hwtable updates and minor cleanups Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH 01/13] multipath-tools: multipathd.8.in: fix mandoc WARNINGs Xose Vazquez Perez
2026-11-16 21:38   ` Benjamin Marzinski
2026-11-18 15:02     ` Xose Vazquez Perez
2026-11-19 17:38       ` Benjamin Marzinski [this message]
2026-11-13 12:55 ` [PATCH 02/13] multipath-tools: hwtable: make no_path_retry independent of DEFAULT_CHECKINT Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH RESEND 03/13] multipath-tools: hwtable: add FUJITSU ETERNUS VX710/VX740 Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH 04/13] multipath-tools: add EMC VNXe info Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH 05/13] multipath-tools: hwtable: update Intel Multi-Flex comment Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH 06/13] multipath-tools: hwtable: update Pivot3 maintainer email address Xose Vazquez Perez
2026-11-13 13:03   ` Bart Brooks
2026-11-13 12:55 ` [PATCH 07/13] multipath-tools: hwtable: update template instructions Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH 09/13] multipath-tools: hwtable: update IBM arrays entries and comments Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH 10/13] multipath-tools: hwtable: add Dell PowerFlex NVMe (formerly iScaleIO/VxFlex OS) Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH 11/13] multipath-tools: hwtable: add Western Digital OpenFlex NVMe Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH v2 12/13] multipath-tools: add repology table to README.md Xose Vazquez Perez
2026-11-13 12:55 ` [PATCH RESEND 13/13] multipath-tools: move SPDX-License-Identifier to the top of create-config.mk and rules.mk Xose Vazquez Perez
2026-11-16 21:40 ` [PATCH 00/13] multipath-tools: hwtable updates and minor cleanups Benjamin Marzinski

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=av80EsBawOfxfHXK@redhat.com \
    --to=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=mwilck@suse.com \
    --cc=xose.vazquez@gmail.com \
    /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.