From: "Darrick J. Wong" <djwong@kernel.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: mkfs: document sample configuration file location
Date: Fri, 17 Dec 2021 13:38:39 -0800 [thread overview]
Message-ID: <20211217213839.GR27664@magnolia> (raw)
In-Reply-To: <86a01a07-630a-6bc3-749d-678037221b1d@sandeen.net>
On Fri, Dec 17, 2021 at 03:05:38PM -0600, Eric Sandeen wrote:
>
>
> On 12/17/21 2:39 PM, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > Update the documentation to note where one can find sample configuration
> > files.
> >
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> > man/man8/mkfs.xfs.8 | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/man/man8/mkfs.xfs.8 b/man/man8/mkfs.xfs.8
> > index 4d292dbe..7984f818 100644
> > --- a/man/man8/mkfs.xfs.8
> > +++ b/man/man8/mkfs.xfs.8
> > @@ -159,6 +159,7 @@ The configuration options will be sourced from the file specified by the
> > option string.
> > This option can be use either an absolute or relative path to the configuration
> > file to be read.
> > +Sample configuration files can be found in /usr/share/xfsprogs/mkfs/.
>
> That path is actually configure-time configurable, right, so ... sorry
> for being a PITA but I'm not sure we should cite a definitive location
> like that in the manpage ..?
Yeah, you're right, this should be autogenerated via sed or something.
--D
>
> > .RE
> > .PP
> > .PD 0
> >
prev parent reply other threads:[~2021-12-17 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 20:39 mkfs: document sample configuration file location Darrick J. Wong
2021-12-17 21:05 ` Eric Sandeen
2021-12-17 21:38 ` Darrick J. Wong [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=20211217213839.GR27664@magnolia \
--to=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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