From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux GFS2 <gfs2@lists.linux.dev>,
Jonathan Corbet <corbet@lwn.net>,
Andreas Gruenbacher <agruenba@redhat.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Randy Dunlap <rdunlap@infradead.org>,
Christian Brauner <brauner@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>, Jan Kara <jack@suse.cz>,
Jeff Layton <jlayton@kernel.org>,
Miklos Szeredi <mszeredi@redhat.com>,
Bernd Schubert <bschubert@ddn.com>,
Chen Linxuan <chenlinxuan@uniontech.com>,
James Morse <james.morse@arm.com>
Subject: Re: [PATCH] Documentation: gfs2: Consolidate GFS2 docs into its own subdirectory
Date: Wed, 27 Aug 2025 08:58:44 +0700 [thread overview]
Message-ID: <aK5mVOTFZhv53M8s@archie.me> (raw)
In-Reply-To: <aK2iTlkp9iA3zESf@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
On Tue, Aug 26, 2025 at 01:02:22PM +0100, Matthew Wilcox wrote:
> On Tue, Aug 26, 2025 at 09:39:13AM +0700, Bagas Sanjaya wrote:
> > Documentation for GFS2 is scattered in three docs that are in
> > Documentation/filesystems/ directory. As these docs are standing out as
> > a group, move them into separate gfs2/ subdirectory.
>
> If this is to be done (and I'm not sure that it should be), why preserve
> the 'gfs2-' prefix on the file names? We know the files pertain to
> gfs2, they're now in the gfs2 directory.
>
I'm just moving files, though.
Anyway, thanks for the suggestion. I'll apply it in v2.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-08-27 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 2:39 [PATCH] Documentation: gfs2: Consolidate GFS2 docs into its own subdirectory Bagas Sanjaya
2025-08-26 12:02 ` Matthew Wilcox
2025-08-27 1:58 ` Bagas Sanjaya [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=aK5mVOTFZhv53M8s@archie.me \
--to=bagasdotme@gmail.com \
--cc=agruenba@redhat.com \
--cc=bhelgaas@google.com \
--cc=brauner@kernel.org \
--cc=bschubert@ddn.com \
--cc=chenlinxuan@uniontech.com \
--cc=corbet@lwn.net \
--cc=djwong@kernel.org \
--cc=gfs2@lists.linux.dev \
--cc=jack@suse.cz \
--cc=james.morse@arm.com \
--cc=jlayton@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=rdunlap@infradead.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).