From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: chao@kernel.org, oliver.yang@linux.alibaba.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] erofs: update the overview of the documentation
Date: Tue, 16 Jun 2026 11:37:17 +0000 [thread overview]
Message-ID: <cf679da5-fbd0-41c6-b5ae-e6a677b98cfd@kernel.org> (raw)
In-Reply-To: <20260610030532.3170375-1-hsiangkao@linux.alibaba.com>
On 6/10/26 03:05, Gao Xiang wrote:
> Update the overview section to better reflect EROFS's design philosophy
> as an immutable image filesystem, update the feature highlights with
> recent capabilities, and remove outdated items.
>
> The following detailed sections will be revised later since the overview
> section is the most visible part of our documentation. Outdated or
> ambiguous information could mislead new users and potential adopters.
>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2026-06-16 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 3:05 [PATCH] erofs: update the overview of the documentation Gao Xiang
2026-06-16 11:37 ` Chao Yu [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=cf679da5-fbd0-41c6-b5ae-e6a677b98cfd@kernel.org \
--to=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.yang@linux.alibaba.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