From: "Darrick J. Wong" <djwong@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 2/2] fuse2fs.1: fix formatting of newly added options in the man page
Date: Wed, 2 Jul 2025 08:19:43 -0700 [thread overview]
Message-ID: <20250702151943.GL9987@frogsfrogsfrogs> (raw)
In-Reply-To: <20250702035044.47373-2-tytso@mit.edu>
On Tue, Jul 01, 2025 at 11:50:44PM -0400, Theodore Ts'o wrote:
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> misc/fuse2fs.1.in | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/misc/fuse2fs.1.in b/misc/fuse2fs.1.in
> index d485ccbdc..21f576074 100644
> --- a/misc/fuse2fs.1.in
> +++ b/misc/fuse2fs.1.in
> @@ -54,7 +54,7 @@ do not replay the journal and mount the file system read-only
> \fB-o\fR fuse2fs_debug
> enable fuse2fs debugging
> .TP
> -.BR -o kernel
> +\fB-o\fR kernel
> Behave more like the kernel ext4 driver in the following ways:
> Allows processes owned by other users to access the filesystem.
> Uses the kernel's permissions checking logic instead of fuse2fs's.
> @@ -63,10 +63,10 @@ Note that these options can still be overridden (e.g.
> .I nosuid
> ) later.
> .TP
> -.BR -o direct
> +\fB-o\fR direct
> Use O_DIRECT to access the block device.
> .TP
> -.BR -o cache_size
> +\fB-o\fR cache_size
> Set the disk cache size to this quantity.
> The quantity may contain the suffixes k, m, or g.
> By default, the size is 32MB.
> --
> 2.47.2
>
>
next prev parent reply other threads:[~2025-07-02 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 3:50 [PATCH 1/2] fuse2fs: fix normal (non-kernel) permissions checking Theodore Ts'o
2025-07-02 3:50 ` [PATCH 2/2] fuse2fs.1: fix formatting of newly added options in the man page Theodore Ts'o
2025-07-02 15:19 ` Darrick J. Wong [this message]
2025-07-02 15:15 ` [PATCH 1/2] fuse2fs: fix normal (non-kernel) permissions checking 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=20250702151943.GL9987@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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