From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>, Miklos Szeredi <miklos@szeredi.hu>
Cc: Christian Brauner <brauner@kernel.org>,
Linux unionfs <linux-unionfs@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 1/2] overlayfs.rst: use consistent terminology
Date: Wed, 13 Dec 2023 12:00:40 +0700 [thread overview]
Message-ID: <ZXk6eNa8n0n1Uerb@archie.me> (raw)
In-Reply-To: <20231212073324.245541-2-amir73il@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
On Tue, Dec 12, 2023 at 09:33:23AM +0200, Amir Goldstein wrote:
> -1) "redirect_dir"
> +redirect_dir
> +````````````
>
> Enabled with the mount option or module option: "redirect_dir=on" or with
> the kernel config option CONFIG_OVERLAY_FS_REDIRECT_DIR=y.
> @@ -568,7 +569,8 @@ the kernel config option CONFIG_OVERLAY_FS_REDIRECT_DIR=y.
> If this feature is disabled, then rename(2) on a lower or merged directory
> will fail with EXDEV ("Invalid cross-device link").
>
> -2) "inode index"
> +index
> +`````
>
> Enabled with the mount option or module option "index=on" or with the
> kernel config option CONFIG_OVERLAY_FS_INDEX=y.
> @@ -577,7 +579,8 @@ If this feature is disabled and a file with multiple hard links is copied
> up, then this will "break" the link. Changes will not be propagated to
> other names referring to the same inode.
>
> -3) "xino"
> +xino
> +````
Why is there section heading conversion above (not mentioned in the patch
description)?
--
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:[~2023-12-13 5:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 7:33 [PATCH 0/2] Fixes to overlayfs documentation Amir Goldstein
2023-12-12 7:33 ` [PATCH 1/2] overlayfs.rst: use consistent terminology Amir Goldstein
2023-12-13 5:00 ` Bagas Sanjaya [this message]
2023-12-13 11:26 ` Amir Goldstein
2023-12-12 7:33 ` [PATCH 2/2] overlayfs.rst: fix ReST formatting Amir Goldstein
2023-12-13 5:16 ` Bagas Sanjaya
2023-12-13 11:58 ` Amir Goldstein
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=ZXk6eNa8n0n1Uerb@archie.me \
--to=bagasdotme@gmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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