From: Matthew Wilcox <willy@infradead.org>
To: Sheriff Esseson <sheriffesseson@gmail.com>
Cc: skhan@linuxfoundation.org, darrick.wong@oracle.com,
linux-xfs@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [linux-kernel-mentees] [PATCH v6] Doc : fs : convert xfs.txt to ReST
Date: Tue, 9 Jul 2019 11:45:59 -0700 [thread overview]
Message-ID: <20190709184559.GL32320@bombadil.infradead.org> (raw)
In-Reply-To: <20190709124859.GA21503@localhost>
On Tue, Jul 09, 2019 at 01:48:59PM +0100, Sheriff Esseson wrote:
> Convert xfs.txt to ReST, rename and fix broken references, consequently.
>
> Signed-off-by: Sheriff Esseson <sheriffesseson@gmail.com>
> ---
>
> Changes in v6:
> - undo text reflow from v5.
> - fix a typo.
> - change indication of defaults , as suggested by Darrick J. Wong, to
> keep the read simple.
> - change delimiter of boolean option from a newline to an "or" (clue
> from something like "<option> and <another option>" in the text)
> because the former does not render well in html.
>
> Documentation/filesystems/dax.txt | 2 +-
> Documentation/filesystems/index.rst | 1 +
> .../filesystems/{xfs.txt => xfs.rst} | 123 +++++++++---------
> MAINTAINERS | 2 +-
> 4 files changed, 61 insertions(+), 67 deletions(-)
> rename Documentation/filesystems/{xfs.txt => xfs.rst} (81%)
Documentation/{filesystem/xfs.txt => admin-guide/xfs.rst}.
> - If "largeio" specified, a filesystem that was created with a
> - "swidth" specified will return the "swidth" value (in bytes)
> - in st_blksize. If the filesystem does not have a "swidth"
> - specified but does specify an "allocsize" then "allocsize"
> + If ``largeio`` specified, a filesystem that was created with a
surely 'If ``largeio`` is specified' here?
> + ``swidth`` specified will return the ``swidth`` value (in bytes)
> + in ``st_blksize``. If the filesystem does not have a ``swidth``
> + specified but does specify an ``allocsize`` then ``allocsize``
> (in bytes) will be returned instead. Otherwise the behaviour
prev parent reply other threads:[~2019-07-09 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 12:48 Sheriff Esseson
2019-07-09 14:05 ` Christoph Hellwig
2019-07-09 18:45 ` Matthew Wilcox [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=20190709184559.GL32320@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sheriffesseson@gmail.com \
--cc=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®