From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
"Darrick J. Wong" <djwong@kernel.org>,
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>,
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 v3] Documentation: xfs: consolidate XFS docs into its own subdirectory
Date: Sat, 9 Dec 2023 15:17:29 +0700 [thread overview]
Message-ID: <9573bd00-7b9e-40d0-9229-f273bf4e6a16@gmail.com> (raw)
In-Reply-To: <874jgryf8d.fsf@debian-BULLSEYE-live-builder-AMD64>
On 12/9/23 15:00, Chandan Babu R wrote:
> On Sat, Dec 09, 2023 at 12:26:43 PM +0700, Bagas Sanjaya wrote:
>> [[PGP Signed Part:No public key for F6B9894955514EA3 created at 2023-12-09T10:56:39+0530 using EDDSA]]
>> On Wed, Nov 29, 2023 at 07:39:47PM +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>
>>
>> Hi Jon, Chandan, and Darrick,
>>
>> FYI, XFS tree [1] is not updated since 2 weeks ago (and this patch doesn't get
>> picked up). Would you like to route this patch through docs-next tree or
>> xfs/for-next?
>>
>
> This patch is part of a collection of patches that I am planning to include in
> the pull request for v6.8-rc1. I am currently running fstests to make sure
> that there are no regressions.
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2023-12-09 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 12:39 [PATCH v3] Documentation: xfs: consolidate XFS docs into its own subdirectory Bagas Sanjaya
2023-11-29 14:49 ` Bill O'Donnell
2023-11-29 16:07 ` Darrick J. Wong
2023-12-09 5:26 ` Bagas Sanjaya
2023-12-09 8:00 ` Chandan Babu R
2023-12-09 8:17 ` 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=9573bd00-7b9e-40d0-9229-f273bf4e6a16@gmail.com \
--to=bagasdotme@gmail.com \
--cc=allison.henderson@oracle.com \
--cc=bhelgaas@google.com \
--cc=chandan.babu@oracle.com \
--cc=corbet@lwn.net \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).