From: "Darrick J. Wong" <djwong@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux XFS <linux-xfs@vger.kernel.org>,
Linux Kernel Workflows <workflows@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Chandan Babu R <chandan.babu@oracle.com>,
Namjae Jeon <linkinjeon@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
Steve French <stfrench@microsoft.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Allison Henderson <allison.henderson@oracle.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Charles Han <hanchunchao@inspur.com>,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH RESEND v2] Documentation: xfs: consolidate XFS docs into its own subdirectory
Date: Tue, 28 Nov 2023 23:17:50 -0800 [thread overview]
Message-ID: <20231129071750.GU36211@frogsfrogsfrogs> (raw)
In-Reply-To: <ZWbkbfjyDJS7jxDg@archie.me>
On Wed, Nov 29, 2023 at 02:12:45PM +0700, Bagas Sanjaya wrote:
> On Tue, Nov 28, 2023 at 09:24:00PM -0800, Darrick J. Wong wrote:
> > On Tue, Nov 28, 2023 at 08:32:55AM -0800, Darrick J. Wong wrote:
> > > On Tue, Nov 28, 2023 at 07:45:22PM +0700, Bagas Sanjaya wrote:
> > > > XFS docs are currently in upper-level Documentation/filesystems.
> > > > Although these are currently 4 docs, they are already outstanding as
> > > > a group and can be moved to its own subdirectory.
> > > >
> > > > Consolidate them into Documentation/filesystems/xfs/.
> > > >
> > > > Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> > > > ---
> > > > Changes since v1 [1]:
> > > >
> > > > * Also update references to old doc path to address kernel test robot
> > > > warnings [2].
> > > >
> > > > [1]: https://lore.kernel.org/linux-doc/20231121095658.28254-1-bagasdotme@gmail.com/
> > > > [2]: https://lore.kernel.org/linux-doc/a9abc5ec-f3cd-4a1a-81b9-a6900124d38b@gmail.com/
> > > >
> > > > Documentation/filesystems/index.rst | 5 +----
> > > > Documentation/filesystems/xfs/index.rst | 14 ++++++++++++++
> > > > .../{ => xfs}/xfs-delayed-logging-design.rst | 0
> > > > .../{ => xfs}/xfs-maintainer-entry-profile.rst | 0
> > > > .../{ => xfs}/xfs-online-fsck-design.rst | 2 +-
> > > > .../{ => xfs}/xfs-self-describing-metadata.rst | 0
> > > > .../maintainer/maintainer-entry-profile.rst | 2 +-
> > > > MAINTAINERS | 4 ++--
> > > > 8 files changed, 19 insertions(+), 8 deletions(-)
> > > > create mode 100644 Documentation/filesystems/xfs/index.rst
> > > > rename Documentation/filesystems/{ => xfs}/xfs-delayed-logging-design.rst (100%)
> > > > rename Documentation/filesystems/{ => xfs}/xfs-maintainer-entry-profile.rst (100%)
> > > > rename Documentation/filesystems/{ => xfs}/xfs-online-fsck-design.rst (99%)
> > > > rename Documentation/filesystems/{ => xfs}/xfs-self-describing-metadata.rst (100%)
> > >
> > > I think the rst filename should drop the 'xfs-' prefix, e.g.
> > >
> > > Documentation/filesystems/xfs/delayed-logging-design.rst
> > >
> > > since that seems to be what most filesystems do:
> >
> > Actually, ignore this suggestion. I forgot that I have vim paths
> > trained on the Documentation/filesystems/ directory, which means I'll
> > lose the ability to
> >
> > :f xfs-online-fsck-design.rst
> >
> > and pop it open. Not that I expect many more filesystems to grow online
> > fsck capabilities, but you get the point...
>
> So is it OK to just move the the docs and keeping their basename intact (as I
> did here)?
Correct.
> > > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > > index ea790149af7951..fd288ac57e19fb 100644
> > > > --- a/MAINTAINERS
> > > > +++ b/MAINTAINERS
> > > > @@ -23893,10 +23893,10 @@ S: Supported
> > > > W: http://xfs.org/
> > > > C: irc://irc.oftc.net/xfs
> > > > T: git git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
> > > > -P: Documentation/filesystems/xfs-maintainer-entry-profile.rst
> > > > +P: Documentation/filesystems/xfs/xfs-maintainer-entry-profile.rst
> > > > F: Documentation/ABI/testing/sysfs-fs-xfs
> > > > F: Documentation/admin-guide/xfs.rst
> > > > -F: Documentation/filesystems/xfs-*
> > > > +F: Documentation/filesystems/xfs/xfs-*
> > >
> > > Shouldn't this be "Documentation/filesystems/xfs/*" ?
> >
> > ...though this suggestion remains standing.
>
> OK, will fix it up in v3.
Ok, thanks!
--D
> --
> An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-11-29 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:45 Bagas Sanjaya
2023-11-28 16:32 ` Darrick J. Wong
2023-11-29 5:24 ` Darrick J. Wong
2023-11-29 7:12 ` Bagas Sanjaya
2023-11-29 7:17 ` Darrick J. Wong [this message]
2023-11-29 16:11 ` Matthew Wilcox
2023-11-29 16:13 ` Darrick J. Wong
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=20231129071750.GU36211@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=bagasdotme@gmail.com \
--cc=bhelgaas@google.com \
--cc=chandan.babu@oracle.com \
--cc=corbet@lwn.net \
--cc=dchinner@redhat.com \
--cc=hanchunchao@inspur.com \
--cc=linkinjeon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stfrench@microsoft.com \
--cc=vegard.nossum@oracle.com \
--cc=willy@infradead.org \
--cc=workflows@vger.kernel.org \
/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