public inbox for linux-unionfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Amir Goldstein <amir73il@gmail.com>
Cc: NeilBrown <neilb@suse.com>,
	linux-unionfs@vger.kernel.org, linux-doc@vger.kernel.org,
	Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH] ovl: fix reStructuredText syntax errors in documentation
Date: Thu, 15 Dec 2016 07:25:53 -0700	[thread overview]
Message-ID: <20161215072553.1beb3ad0@lwn.net> (raw)
In-Reply-To: <CAOQ4uxg8s_1ATqFFD6__2dez9-VYqR2NpFQ5iU8zvCDYLib0Pw@mail.gmail.com>

On Thu, 15 Dec 2016 09:58:31 +0200
Amir Goldstein <amir73il@gmail.com> wrote:

> Ping.

Patches that show up right before the merge window opens can get the
back-burner treatment for a bit, sorry.

> Neil,
> I found these syntax errors when I posted your page on my wiki:
> https://github.com/amir73il/overlayfs/wiki/Overlayfs-overview
> 
The "errors" are unsurprising, given that this is not (yet) an RST file.

What we would *really* like to do is integrate this into the growing body
of Sphinx documentation.  That involves thinking about where filesystem
documentation goes in that world, either in the admin manual or into a
new one.

Meanwhile, though, the RST conversion on this file is a fine thing to do,
and I'll be happy to apply the patch once I start working on 4.11 stuff.

Thanks,

jon

  reply	other threads:[~2016-12-15 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08  7:49 [PATCH] ovl: fix reStructuredText syntax errors in documentation Amir Goldstein
2016-12-15  7:58 ` Amir Goldstein
2016-12-15 14:25   ` Jonathan Corbet [this message]
2016-12-15 21:12   ` NeilBrown

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=20161215072553.1beb3ad0@lwn.net \
    --to=corbet@lwn.net \
    --cc=amir73il@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neilb@suse.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