All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Martin Wilck <mwilck@suse.com>
Cc: Benjamin Marzinski <bmarzins@redhat.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>,
	DM_DEVEL-ML <dm-devel@lists.linux.dev>
Subject: Re: [PATCH 2/2] multipath-tools: add mandoc check to man pages
Date: Sat, 13 Jun 2026 14:09:58 +0200	[thread overview]
Message-ID: <403580ab-e195-4a9e-a080-9487add2eaaf@gmail.com> (raw)
In-Reply-To: <cd074f884f847ed291c2e720657668d6a0523f8f.camel@suse.com>

On 10/10/25 1:20 PM, Martin Wilck wrote:

> On Fri, 2025-10-10 at 11:22 +0200, Xose Vazquez Perez wrote:
>> Cc: Martin Wilck <mwilck@suse.com>
>> Cc: Benjamin Marzinski <bmarzins@redhat.com>
>> Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>
>> Cc: DM_DEVEL-ML <dm-devel@lists.linux.dev>
>> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
>> ---
>>   kpartx/kpartx.8                                | 1 +
>>   libmpathpersist/mpath_persistent_reserve_in.3  | 1 +
>>   libmpathpersist/mpath_persistent_reserve_out.3 | 1 +
>>   mpathpersist/mpathpersist.8.in                 | 5 +++--
>>   multipath/multipath.8.in                       | 5 +++--
>>   multipath/multipath.conf.5.in                  | 5 +++--
>>   multipathd/multipathc.8                        | 1 +
>>   multipathd/multipathd.8.in                     | 5 +++--
>>   8 files changed, 16 insertions(+), 8 deletions(-)
>>
>> diff --git a/kpartx/kpartx.8 b/kpartx/kpartx.8
>> index ef8051a5..2a55c96b 100644
>> --- a/kpartx/kpartx.8
>> +++ b/kpartx/kpartx.8
>> @@ -2,6 +2,7 @@
>>   .\" Make sure there are no errors with:
>>   .\" groff -z -wall -b -e -t kpartx/kpartx.8
>>   .\" man --warnings -E UTF-8 -l -Tutf8 -Z  kpartx/kpartx.8 >
>> /dev/null
>> +.\" mandoc -W all -T lint kpartx/kpartx.8

> Nack. We don't need this in every man page. Actually, we don't need the
> other command lines mentioned in the man pages, either. While looking
> at this, I realize that the "groff" command line is wrong. AFAICT it
> should be
> 
>     groff -man -z -wall -b -e -t -Tutf8 $MANPAGE_FILE
> 
> But really, it makes no sense to me to have these reminders in every
> man page. If we want to keep our man pages in order (which is of course
> a worthwhile goal), we should rather write a GitHub workflow to check
> them. That would be a helpful contribution.
> 
> I would still question whether our man pages need to pass 3 different
> commands. AFAICS the "groff" and "man" commands are basically
> equivalent anyway, as "man" simply calls "groff" for the parsing and
> formatting. Wrt mandoc in general, see my reply to patch 1/2.
> 
> Regards,
> Martin


I will withdraw this patch. Instead, I will send a new one to
completely remove those groff/man comment lines from all files
to clean them up.

  reply	other threads:[~2026-06-13 12:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10  9:22 [PATCH 1/2] multipath-tools: fix mandoc errors in man pages Xose Vazquez Perez
2025-10-10  9:22 ` [PATCH 2/2] multipath-tools: add mandoc check to " Xose Vazquez Perez
2025-10-10 11:20   ` Martin Wilck
2026-06-13 12:09     ` Xose Vazquez Perez [this message]
2025-10-10 11:20 ` [PATCH 1/2] multipath-tools: fix mandoc errors in " Martin Wilck
2025-10-10 12:37   ` Xose Vazquez Perez
2025-10-10 13:05     ` Martin Wilck
2025-10-15 22:00       ` Xose Vazquez Perez
2026-05-27 20:21       ` Xose Vazquez Perez
2026-06-13 12:04   ` Xose Vazquez Perez

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=403580ab-e195-4a9e-a080-9487add2eaaf@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=mwilck@suse.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.