From: Jonathan Corbet <corbet@lwn.net>
To: Sheriff Esseson <sheriffesseson@gmail.com>
Cc: skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
"supporter:XFS FILESYSTEM" <linux-xfs@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: fs: Convert xfs-delayed-logging-design.txt to ReSt
Date: Tue, 6 Aug 2019 11:46:40 -0600 [thread overview]
Message-ID: <20190806114640.7eeb3f13@lwn.net> (raw)
In-Reply-To: <20190806090323.GA16095@localhost>
On Tue, 6 Aug 2019 10:03:23 +0100
Sheriff Esseson <sheriffesseson@gmail.com> wrote:
> Convert xfs-delayed-logging-design.txt to ReST and fix broken references.
> The enumerations at "Lifecycle Changes" breaks because of lines begining with
> "<", treat as diagrams.
[...]
> @@ -27,14 +30,18 @@ written to disk after change D, we would see in the log the following series
> of transactions, their contents and the log sequence number (LSN) of the
> transaction:
>
> + ============ ========= ==============
> Transaction Contents LSN
> + ============ ========= ==============
> A A X
> B A+B X+n
> C A+B+C X+n+m
> D A+B+C+D X+n+m+o
> <object written to disk>
> - E E Y (> X+n+m+o)
> + ------------------------------------------------------
> + E E Y (> X+n+m+o)
> F E+F Y+p
> + ============ ========= ==============
So this is really more of a diagram than a table; I'd suggest just using a
literal block like you did elsewhere.
[...]
> Lifecycle Changes
> +=================
>
> -The existing log item life cycle is as follows:
> +The existing log item life cycle is as follows::
>
> 1. Transaction allocate
> 2. Transaction reserve
This, instead, is a proper outline. I guess the literal block is OK, but
it feels like we could do better.
Thanks,
jon
prev parent reply other threads:[~2019-08-06 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 9:03 [PATCH] Documentation: fs: Convert xfs-delayed-logging-design.txt to ReSt Sheriff Esseson
2019-08-06 17:46 ` Jonathan Corbet [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=20190806114640.7eeb3f13@lwn.net \
--to=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;
as well as URLs for NNTP newsgroup(s).