From: Gao Xiang <gaoxiang25@huawei.com>
To: Pratik Shinde <pratikshinde320@gmail.com>
Cc: linux-erofs@lists.ozlabs.org
Subject: Re: New things in erofs
Date: Tue, 29 Oct 2019 21:31:38 +0800 [thread overview]
Message-ID: <20191029133138.GA114663@architecture4> (raw)
In-Reply-To: <CAGu0czQfmMoSa-Sm9t+ZYf2b_YAfZ2b2-qPyTAbYvYHB5z-hDw@mail.gmail.com>
Hi Pratik,
On Tue, Oct 29, 2019 at 06:46:56PM +0530, Pratik Shinde wrote:
> Hi Gao,
>
> Thanks.
> I am exploring following things in erofs:
> 1) Sparse file support for uncompressed files.
> 2) erofs.fsck(erofs-utils)
>
> I hope above items are in the development plan & patches are accepted for
> them :)
Yes, they are definitely in the development plan, it would be appreciated
that you take some time to get them in shape if you have time. :-)
You can post RFC patch at any time, I will help on this as well.
For erofs.fsck (erofs-utils), it's better to share most common code in
"lib/" with mkfs.erofs.
Thanks,
Gao Xiang
>
> --Pratik.
>
> On Sat, Oct 26, 2019 at 4:54 PM Gao Xiang <hsiangkao@aol.com> wrote:
>
> > Hi Pratik,
> >
> > On Sat, Oct 26, 2019 at 12:56:10PM +0530, Pratik Shinde wrote:
> > > Hi Gao,
> > >
> > > Are there any new features/enhancements coming in erofs. Something that
> > we
> > > can contribute to?
> > >
> > > P. S. - I saw your erofs roadmap pdf on github.
> >
> > Thanks for your interest. As I mentioned before, I'm currently working on
> > adding a new XZ algorithm to erofs-utils because I'd like to make the
> > decompression framework more powerful and generic...
> >
> > And there are many TODOs in the roadmap pdf, you can pick up something
> > if you have some time or you can raise up some new ideas. It's very
> > helpful to make EROFS better.
> >
> > Thanks,
> > Gao Xiang
> >
> > >
> > > --Pratik
> >
prev parent reply other threads:[~2019-10-29 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 7:26 New things in erofs Pratik Shinde
2019-10-26 11:24 ` Gao Xiang via Linux-erofs
2019-10-29 13:16 ` Pratik Shinde
2019-10-29 13:31 ` Gao Xiang [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=20191029133138.GA114663@architecture4 \
--to=gaoxiang25@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=pratikshinde320@gmail.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