linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang via Linux-erofs <linux-erofs@lists.ozlabs.org>
To: Huang Jianan <huangjianan@oppo.com>
Cc: guoweichao@oppo.com, linux-erofs@lists.ozlabs.org, zhangshiming@oppo.com
Subject: Re: [PATCH 0/5] erofs-utils: support read special file and compressed file for fuse framework
Date: Thu, 15 Oct 2020 22:51:58 +0800	[thread overview]
Message-ID: <20201015145147.GA20107@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <20201015133741.60943-1-huangjianan@oppo.com>

Hi Jianan,

On Thu, Oct 15, 2020 at 09:37:41PM +0800, Huang Jianan wrote:
> Fix some bugs in directory tree parsing.
> Support read special file and compressed file now.
> 
> Huang Jianan (5):
>   erofs-utils: fix the conflict with the master branch
>   erofs-utils: fix the wrong name length of tail file in the directory
>   erofs-utils: fix the wrong address of inline dir content.
>   erofs-utils: support read special file
>   erofs-utils: support read compressed file

Nice job, thanks! I think we definitely need to merge erofsfuse
for erofs-utils v1.2. Therefore all new upcoming features can
have a simple way to verify its on-disk implementation with
erofsfuse first and then think about a more performance-optimized
way for kernel.

Let me play for a while this weekend! And wonder if Guifu could
also look into that as well.

Thanks,
Gao Xiang


      reply	other threads:[~2020-10-15 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 13:37 [PATCH 0/5] erofs-utils: support read special file and compressed file for fuse framework Huang Jianan
2020-10-15 14:51 ` Gao Xiang via Linux-erofs [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=20201015145147.GA20107@hsiangkao-HP-ZHAN-66-Pro-G1 \
    --to=linux-erofs@lists.ozlabs.org \
    --cc=guoweichao@oppo.com \
    --cc=hsiangkao@aol.com \
    --cc=huangjianan@oppo.com \
    --cc=zhangshiming@oppo.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).