linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux Documentation <linux-doc@vger.kernel.org>,
	 Linux Filesystems Development <linux-fsdevel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	 Luis Henriques <luis@igalia.com>,
	Bernd Schubert <bschubert@ddn.com>,
	Amir Goldstein <amir73il@gmail.com>,
	 Chen Linxuan <chenlinxuan@uniontech.com>,
	Christian Brauner <brauner@kernel.org>,
	 "Darrick J. Wong" <djwong@kernel.org>,
	Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
	 James Morse <james.morse@arm.com>
Subject: Re: [PATCH] Documentation: fuse: Consolidate FUSE docs into its own subdirectory
Date: Thu, 12 Jun 2025 11:07:13 +0200	[thread overview]
Message-ID: <CAJfpegvKvKB+1Q23Gm8TKAmb4hPNnSHpK5W29JmDjHVWrWk73Q@mail.gmail.com> (raw)
In-Reply-To: <20250612032239.17561-1-bagasdotme@gmail.com>

On Thu, 12 Jun 2025 at 05:22, Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> All four FUSE docs are currently in upper-level
> Documentation/filesystems/ directory, but these are distinct as a group
> of its own. Move them into Documentation/filesystems/fuse/ subdirectory.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>

Applied, thanks.

Miklos

  reply	other threads:[~2025-06-12  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12  3:22 [PATCH] Documentation: fuse: Consolidate FUSE docs into its own subdirectory Bagas Sanjaya
2025-06-12  9:07 ` Miklos Szeredi [this message]
2025-06-12  9:09 ` Bernd Schubert
2025-06-12 10:53 ` Jeff Layton

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=CAJfpegvKvKB+1Q23Gm8TKAmb4hPNnSHpK5W29JmDjHVWrWk73Q@mail.gmail.com \
    --to=miklos@szeredi.hu \
    --cc=amir73il@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=brauner@kernel.org \
    --cc=bschubert@ddn.com \
    --cc=chenlinxuan@uniontech.com \
    --cc=corbet@lwn.net \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=james.morse@arm.com \
    --cc=jlayton@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis@igalia.com \
    /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).