archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <>
To: "Tobin C. Harding" <>
Cc: Al Viro <>,
	Eric Biggers <>,,
	"Tobin C. Harding" <>
Subject: Re: [PATCH 0/4] vfs: update ->get_link() related documentation
Date: Fri, 3 May 2019 06:16:54 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20190501041515.GA9149@eros.localdomain>

On Wed, 1 May 2019 14:15:15 +1000
"Tobin C. Harding" <> wrote:

> Since the conversion set I did did not fundamentally change the content
> but just moved it to the source files it seemed like this set was a dead
> end.
> FWIW I don't think that a _simple_ conversion for vfs.txt to vfs.rst is
> useful if the VFS is to be re-documented.  It isn't trivial to do if we
> want to make any use of RST features and if we do not want to then why
> bother converting it?

I think it's worth converting; it's sufficiently better than nothing,
IMO, that we don't want to just throw it away.  If we bring it up to
current formatting standards and make it more accessible, it just might
motivate others to help make it better.  So if you feel like sending me a
current patch set, I'd be happy to apply it.



      reply	other threads:[~2019-05-03 12:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 23:16 [PATCH 0/4] vfs: update ->get_link() related documentation Eric Biggers
2019-04-11 23:16 ` [PATCH 1/4] Documentation/filesystems/vfs.txt: remove bogus "Last updated" date Eric Biggers
2019-04-11 23:16 ` [PATCH 2/4] Documentation/filesystems/vfs.txt: document how ->i_link works Eric Biggers
2019-04-11 23:16 ` [PATCH 3/4] Documentation/filesystems/Locking: fix ->get_link() prototype Eric Biggers
2019-04-11 23:16 ` [PATCH 4/4] libfs: document simple_get_link() Eric Biggers
2019-04-22 18:03 ` [PATCH 0/4] vfs: update ->get_link() related documentation Eric Biggers
2019-05-01  0:25   ` Eric Biggers
2019-05-01  1:36     ` Al Viro
2019-05-01  1:49       ` Jonathan Corbet
2019-05-01  2:14         ` Al Viro
2019-05-01  2:17           ` Jonathan Corbet
2019-05-01  4:00             ` Al Viro
2019-05-01  4:15           ` Tobin C. Harding
2019-05-03 12:16             ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).