From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Takahiro Itazuri <itazur@amazon.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: bp@alien8.de, itazur@amazon.com, zulinx86@gmail.com,
jpoimboe@kernel.org, pawan.kumar.gupta@linux.intel.com,
peterz@infradead.org, tglx@linutronix.de
Subject: Re: [PATCH v2] Documentation: Use grid table over list table
Date: Fri, 06 Sep 2024 07:45:12 -0600 [thread overview]
Message-ID: <87h6asgal3.fsf@trenco.lwn.net> (raw)
In-Reply-To: <87zfoknc9y.fsf@intel.com>
Jani Nikula <jani.nikula@linux.intel.com> writes:
> On Fri, 06 Sep 2024, Takahiro Itazuri <itazur@amazon.com> wrote:
>> Using a simple table, a line break in the first column would be
>> recognized as two rows. To avoid that, list table was used but it
>> is unreadable for plain text readers. Uses grid table instead.
>>
>> Signed-off-by: Takahiro Itazuri <itazur@amazon.com>
>> ---
>> Changes in v2:
>> - Use grid table over list table (applying to not only GDS but also
>> other vulnerabilities)
>> - Link to v1: https://lore.kernel.org/all/20240903132533.26458-1-itazur@amazon.com/
>
> I see that Jon asked you to use a grid table.
>
> But when I look at what's being changed, I can't help but think a
> definition list [1] might provide the best compromise between readable
> (and easily editable!) source rst and generated html. I don't think it
> has to be a *table* in either.
>
> Up to Jon, of course.
I think it's up to the people who write and use the documentation in the
end; I don't want to dictate minor choices like that. Anything that
makes it more readable works well for me.
Thanks,
jon
next prev parent reply other threads:[~2024-09-06 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 10:49 [PATCH v2] Documentation: Use grid table over list table Takahiro Itazuri
2024-09-06 13:26 ` Jani Nikula
2024-09-06 13:45 ` Jonathan Corbet [this message]
2024-09-06 17:23 ` Pawan Gupta
2024-09-08 15:50 ` Takahiro Itazuri
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=87h6asgal3.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bp@alien8.de \
--cc=itazur@amazon.com \
--cc=jani.nikula@linux.intel.com \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=zulinx86@gmail.com \
/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).