From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
Eric Biggers <ebiggers@kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [f2fs-dev] [PATCH] docs: f2fs: fix a broken table
Date: Tue, 23 Jun 2020 07:57:54 +0200 [thread overview]
Message-ID: <20200623075754.093c476d@coco.lan> (raw)
In-Reply-To: <20200622112209.71990f9c@lwn.net>
Em Mon, 22 Jun 2020 11:22:09 -0600
Jonathan Corbet <corbet@lwn.net> escreveu:
> On Mon, 22 Jun 2020 10:11:06 -0700
> Eric Biggers <ebiggers@kernel.org> wrote:
>
> > Someone already sent out a fix for this:
> > https://lkml.kernel.org/linux-doc/52f851cb5c9fd2ecae97deec7e168e66b8c295c3.1591137229.git.mchehab+huawei@kernel.org/
No problem from my side.
> >
> > Is it intentional that you're sending out a different fix rather than applying
> > that one?
>
> It wasn't, actually, I'm just finding myself more than usually challenged
> these days.
>
> That said, removing the table entirely seems ... excessive. It's not
> terrible the way it is, or we could make it:
Jon,
I actually tried a patch close to yours before the patch I actually sent
upstream.
On my previous version, I was doing:
======================== =======================================================
...
test_dummy_encryption
test_dummy_encryption=%s Enable dummy encryption, which provides a fake fscrypt
context. The fake fscrypt context is used by xfstests.
The argument may be either "v1" or "v2", in order to
select the corresponding fscrypt policy version.
...
======================== =======================================================
The problem with the above is that Sphinx understood the first line as one row,
and the second one as a different one. So, the HTML output would be like:
<table>
...
<tr><td>test_dummy_encryption</td></tr>
<tr><td>test_dummy_encryption=%s</td>
<td>Enable dummy encryption, which provides a fake fscrypt
context. The fake fscrypt context is used by xfstests.
The argument may be either "v1" or "v2", in order to
select the corresponding fscrypt policy version.</td>
</tr>
(e. g. it would look like the first parameter lacks description)
Which is not the intended result. I was unable to identify a way
to teach Sphinx that the second line was a continuation of the
first (A ReST equivalent to placing a \ at the end of a line).
Still, the html output with the above is not that bad, and it should be clear
for readers that the description of the second parameter is also valid for the
first.
Thanks,
Mauro
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2020-06-23 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200622073907.7608a73a@lwn.net>
2020-06-22 17:11 ` [f2fs-dev] [PATCH] docs: f2fs: fix a broken table Eric Biggers
2020-06-22 17:22 ` Jonathan Corbet
2020-06-23 5:57 ` Mauro Carvalho Chehab [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=20200623075754.093c476d@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).