From: Yue Hu <zbestahu@gmail.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: linux-erofs@lists.ozlabs.org, zhangwen@coolpad.com
Subject: Re: [PATCH 3/3] erofs-utils: add `-Eall-fragments` option
Date: Wed, 1 Mar 2023 19:21:49 +0800 [thread overview]
Message-ID: <20230301192149.000070db.zbestahu@gmail.com> (raw)
In-Reply-To: <20230228185459.117762-3-hsiangkao@linux.alibaba.com>
On Wed, 1 Mar 2023 02:54:59 +0800
Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
> It's almost the same as `-Efragments` option, except that will
> explicitly pack the whole data into the special inode instead.
>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Tested-by: Yue Hu <huyue2@coolpad.com>
next prev parent reply other threads:[~2023-03-01 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 18:54 [PATCH 1/3] erofs-utils: get rid of useless nr_dup Gao Xiang
2023-02-28 18:54 ` [PATCH 2/3] erofs-utils: use compressed pclusters to mark fragments Gao Xiang
2023-03-01 14:00 ` Yue Hu
2023-02-28 18:54 ` [PATCH 3/3] erofs-utils: add `-Eall-fragments` option Gao Xiang
2023-03-01 11:21 ` Yue Hu [this message]
2023-03-01 11:05 ` [PATCH 1/3] erofs-utils: get rid of useless nr_dup Yue Hu
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=20230301192149.000070db.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=zhangwen@coolpad.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