All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
	linux-ext4@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] docs: promote the ext4 data structures book to top level
Date: Sun, 7 Oct 2018 08:45:14 -0600	[thread overview]
Message-ID: <20181007084514.57c945d0@lwn.net> (raw)
In-Reply-To: <20181005234952.GC2548@thunk.org>

On Fri, 5 Oct 2018 19:49:52 -0400
"Theodore Y. Ts'o" <tytso@mit.edu> wrote:

> On Thu, Oct 04, 2018 at 05:59:44PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> > 
> > Move the ext4 data structures book to Documentation/filesystems/ext4/
> > since the administrative information moved elsewhere.
> > 
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>  
> 
> Thanks, applied and pushed out to the ext4.git tree.
> 
> Randy, Jon: the original patch didn't make it past vger.kernel.org
> because it was too large (it was moving a lot of files around).  It
> looked fine to me, but if you want to take a look it should be on the
> dev branch of the ext4.git tree.

FWIW, from a quick look it seems fine to me.

   Acked-by: Jonathan Corbet <corbet@lwn.net>

(though I expect it's too late to add that).

jon

      reply	other threads:[~2018-10-07 21:52 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 ` [PATCH 0/2] ext4: even more documentation fixes Randy Dunlap
2018-10-05 15:22   ` 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 [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=20181007084514.57c945d0@lwn.net \
    --to=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.