All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: Anthony Iliopoulos <ailiop@suse.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfs: use -w instead of --path for man program portability
Date: Tue, 4 Aug 2026 22:16:03 +1000	[thread overview]
Message-ID: <20260804221603.0d48ad17.ddiss@suse.de> (raw)
In-Reply-To: <20260803115819.17110-1-ailiop@suse.com>

Looks fine.
Reviewed-by: David Disseldorp <ddiss@suse.de>

On Mon,  3 Aug 2026 13:58:19 +0200, Anthony Iliopoulos wrote:

> Some implementations of man(1) do not support the long option --path to
> display the actual location of a man page, which can cause these tests
> to fail on systems using alternative man packages, such as mandoc.
> 
> Switch to using the more standard -w flag across these tests to improve
> portability while maintaining the same behavior

The mandoc man.options.1 page seems to do a pretty good job of
tracking where the various flags appear across man utils.

  reply	other threads:[~2026-08-04 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 11:58 [PATCH] xfs: use -w instead of --path for man program portability Anthony Iliopoulos
2026-08-04 12:16 ` David Disseldorp [this message]
2026-08-10 21:31 ` Zorro Lang

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=20260804221603.0d48ad17.ddiss@suse.de \
    --to=ddiss@suse.de \
    --cc=ailiop@suse.com \
    --cc=fstests@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 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.