linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 22/34] docs: filesystems: rename path-lookup.txt file
Date: Wed, 15 Apr 2020 19:00:06 -0700	[thread overview]
Message-ID: <20200416020006.GC816@sol.localdomain> (raw)
In-Reply-To: <ddee231f968fcf8a9558ff39f251fdd7b2357ff2.1586960617.git.mchehab+huawei@kernel.org>

On Wed, Apr 15, 2020 at 04:32:35PM +0200, Mauro Carvalho Chehab wrote:
> There are two files called "patch-lookup", with different contents:
> one is a ReST file, the other one is the text.
> 
> As we'll be finishing the conversion of filesystem documents,
> let's fist rename the text one, in order to avoid messing with
> the existing ReST file.
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
>  .../filesystems/{path-lookup.txt => path-walking.txt}       | 0
>  Documentation/filesystems/porting.rst                       | 2 +-
>  fs/dcache.c                                                 | 6 +++---
>  fs/namei.c                                                  | 2 +-
>  4 files changed, 5 insertions(+), 5 deletions(-)
>  rename Documentation/filesystems/{path-lookup.txt => path-walking.txt} (100%)

Wouldn't it make more sense to consolidate path-lookup.rst and path-lookup.txt
into one file?  The .txt one is less detailed and hasn't been updated since
2011, so maybe it should just be deleted?  Perhaps there's something useful in
it that should be salvaged, though.

- Eric

  reply	other threads:[~2020-04-16  2:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 14:32 [PATCH 00/34] fs: convert remaining docs to ReST file format Mauro Carvalho Chehab
2020-04-15 14:32 ` [PATCH 01/34] docs: filesystems: fix references for doc files there Mauro Carvalho Chehab
2020-04-16  1:10   ` Joseph Qi
2020-04-15 14:32 ` [PATCH 14/34] docs: filesystems: convert dnotify.txt to ReST Mauro Carvalho Chehab
2020-04-16  8:45   ` Jan Kara
2020-04-15 14:32 ` [PATCH 20/34] docs: filesystems: convert mandatory-locking.txt " Mauro Carvalho Chehab
2020-04-15 14:32 ` [PATCH 22/34] docs: filesystems: rename path-lookup.txt file Mauro Carvalho Chehab
2020-04-16  2:00   ` Eric Biggers [this message]
2020-04-21 16:38     ` Mauro Carvalho Chehab
2020-04-15 14:32 ` [PATCH 23/34] docs: filesystems: convert path-walking.txt to ReST Mauro Carvalho Chehab
2020-04-15 14:32 ` [PATCH 26/34] docs: filesystems: convert sharedsubtree.txt " Mauro Carvalho Chehab

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=20200416020006.GC816@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).