All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>, tytso@mit.edu
Cc: linux-ext4@vger.kernel.org, linux-doc@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH 0/2] ext4: even more documentation fixes
Date: Thu, 4 Oct 2018 19:48:31 -0700	[thread overview]
Message-ID: <007a23b2-1db3-36fb-3300-f94115d4f2b3@infradead.org> (raw)
In-Reply-To: <153870117116.30837.1220267868954289184.stgit@magnolia>

On 10/4/18 5:59 PM, Darrick J. Wong wrote:
> Hi all,
> 
> This series fixes some problems that were brought up during review for
> the XFS documentation which I hadn't known about when pushing the ext4
> documentation during the 4.19 cycle.
> 
> The first patch moves the ext4 mount option and sysfs knob information
> into the Linux administration guide.
> 
> The second patch moves the ext4 Data Structures & Algorithms book up a
> level since it's a self-contained documentation book.
> 
> I've built the docs and put them here, in case you hate reading rst:
> https://djwong.org/docs/kdoc/filesystems/ext4/index.html
> 
> The patchset should apply cleanly against 4.19-rc6.  Comments and
> questions are, as always, welcome.

Hi Darrick,

I don't see patch 2/2 anywhere (my inbox, email archives)...

-- 
~Randy

  parent reply	other threads:[~2018-10-05  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05  0:59 [PATCH 0/2] ext4: even more documentation fixes Darrick J. Wong
2018-10-05  0:59 ` [PATCH 1/2] docs: move ext4 administrative docs to admin-guide/ Darrick J. Wong
2018-10-05  2:48 ` Randy Dunlap [this message]
2018-10-05 15:22   ` [PATCH 0/2] ext4: even more documentation fixes Theodore Y. Ts'o
2018-10-05 15:33     ` Randy Dunlap
     [not found] ` <153870118415.30837.3990077919915459798.stgit@magnolia>
2018-10-05 23:49   ` [PATCH 2/2] docs: promote the ext4 data structures book to top level Theodore Y. Ts'o
2018-10-07 14:45     ` Jonathan Corbet

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=007a23b2-1db3-36fb-3300-f94115d4f2b3@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=darrick.wong@oracle.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-ext4@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 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.