From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
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>,
Randy Dunlap <rdunlap@infradead.org>,
Bjorn Helgaas <bhelgaas@google.com>, Jan Kara <jack@suse.cz>,
Christian Brauner <brauner@kernel.org>,
Miklos Szeredi <mszeredi@redhat.com>,
Jeff Layton <jlayton@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
James Morse <james.morse@arm.com>,
Bernd Schubert <bschubert@ddn.com>,
Chen Linxuan <chenlinxuan@uniontech.com>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v4] Documentation: gfs2: Consolidate GFS2 docs into its own subdirectory
Date: Wed, 24 Sep 2025 06:03:37 +0700 [thread overview]
Message-ID: <aNMnSapfyfwga0Oz@archie.me> (raw)
In-Reply-To: <CAHc6FU7aGJZZzN8zhtnwDgXX9gVMh_fbi+sUpJ7tg1MWMa8XVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
On Tue, Sep 23, 2025 at 01:44:18PM +0200, Andreas Gruenbacher wrote:
> On Tue, Sep 23, 2025 at 1:00 PM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> > On Thu, Sep 11, 2025 at 07:44:17AM +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.
> >
> > Hi Andreas,
> >
> > It looks like this patch isn't in 6.18 PR [1]. Should I resend it after
> > merge window (and for 6.19 instead)?
>
> Ah, I was already wondering what had happened to that patch.
>
> Can we just put this into the next (6.20?) merge window?
OK, I will resend after 6.18-rc1 is out.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-09-23 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 0:44 [PATCH v4] Documentation: gfs2: Consolidate GFS2 docs into its own subdirectory Bagas Sanjaya
2025-09-23 11:00 ` Bagas Sanjaya
2025-09-23 11:44 ` Andreas Gruenbacher
2025-09-23 23:03 ` Bagas Sanjaya [this message]
2025-09-24 12:17 ` Andreas Gruenbacher
2025-09-24 12:54 ` Bagas Sanjaya
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=aNMnSapfyfwga0Oz@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