From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Neil Brown <neilb@suse.com>, Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/9] docs: Convert VFS doc to RST
Date: Thu, 30 May 2019 16:01:30 +1000 [thread overview]
Message-ID: <20190530060130.GB11021@caerus> (raw)
In-Reply-To: <20190529163052.6ce91581@lwn.net>
On Wed, May 29, 2019 at 04:30:52PM -0600, Jonathan Corbet wrote:
> On Wed, 15 May 2019 10:29:04 +1000
> "Tobin C. Harding" <tobin@kernel.org> wrote:
>
> > Here is an updated version of the VFS doc conversion. This series in no
> > way represents a final point for the VFS documentation rather it is a
> > small step towards getting VFS docs updated. This series does not
> > update the content of vfs.txt, only does formatting.
>
> I've finally gotten to this, sorry for taking so long. Applying it to
> docs-next turned out to be a bit of a chore; there have been intervening
> changes to vfs.txt that we didn't want to lose. But I did it.
>
> Unfortunately, there's still a remaining issue. You did a lot of list
> conversions like this:
>
> > - struct file_system_type *fs_type: describes the filesystem, partly initialized
> > +``struct file_system_type *fs_type``: describes the filesystem, partly initialized
> > by the specific filesystem code
>
> but that does not render the way you would like, trust me. You really
> want to use the list format, something like:
>
> ``struct file_system_type *fs_type``
> describes the filesystem, partly initialized by the specific
> filesystem code
Ouch! Yes I knew this was sub-optimal, I thought the HTML looked ok.
I'll fix them up as suggested.
> There are, unfortunately, a lot of these to fix... I bet it could be done
> with an elisp function, but I don't have time to beat my head against that
> wall right now.
oh really? That would actually make doing this much more enticing, I've
already done all these multiple times manually - learning nothing, some
elisp games would actually teach me something. Cheers.
> Any chance you would have time to send me a followup patch fixing these
> up? I'll keep my branch with this set for now so there's no need to
> rebase those.
Sure thing, patches to come.
Cheers,
Tobin.
next prev parent reply other threads:[~2019-05-30 6:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 0:29 [PATCH v4 0/9] docs: Convert VFS doc to RST Tobin C. Harding
2019-05-15 0:29 ` [PATCH v4 1/9] docs: filesystems: vfs: Remove space before tab Tobin C. Harding
2019-05-15 0:29 ` [PATCH v4 2/9] docs: filesystems: vfs: Use uniform space after period Tobin C. Harding
2019-05-15 0:29 ` [PATCH v4 3/9] docs: filesystems: vfs: Use 72 character column width Tobin C. Harding
2019-05-15 0:29 ` [PATCH v4 4/9] docs: filesystems: vfs: Use uniform spacing around headings Tobin C. Harding
2019-05-15 0:29 ` [PATCH v4 5/9] docs: filesystems: vfs: Use correct initial heading Tobin C. Harding
2019-05-15 0:29 ` [PATCH v4 6/9] docs: filesystems: vfs: Use SPDX identifier Tobin C. Harding
2019-05-15 0:29 ` [PATCH v4 7/9] docs: filesystems: vfs: Fix pre-amble indentation Tobin C. Harding
2019-05-15 0:29 ` [PATCH v4 8/9] docs: filesystems: vfs: Convert spaces to tabs Tobin C. Harding
2019-05-15 0:29 ` [PATCH v4 9/9] docs: filesystems: vfs: Convert vfs.txt to RST Tobin C. Harding
2019-05-29 22:30 ` [PATCH v4 0/9] docs: Convert VFS doc " Jonathan Corbet
2019-05-30 6:01 ` Tobin C. Harding [this message]
2019-06-03 23:48 ` Tobin C. Harding
2019-06-04 0:06 ` Tobin C. Harding
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=20190530060130.GB11021@caerus \
--to=me@tobin.cc \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=neilb@suse.com \
--cc=rdunlap@infradead.org \
--cc=tobin@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.