From: "zhangyi (F)" <yi.zhang@huawei.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>, Miao Xie <miaoxie@huawei.com>,
yangerkun <yangerkun@huawei.com>
Subject: Re: [ANNOUNCE] fsck.overlayfs: update master branch
Date: Thu, 1 Feb 2018 12:16:21 +0800 [thread overview]
Message-ID: <2b05eb7b-63f2-39c9-1009-7199e94de7fe@huawei.com> (raw)
In-Reply-To: <CAOQ4uxjk8F-a4s7JdcFJXWeU9+VD-b3dddagQjVWEg0F=+5ftg@mail.gmail.com>
On 2018/2/1 4:23, Amir Goldstein Wrote:
> On Wed, Jan 31, 2018 at 12:23 PM, zhangyi (F) <yi.zhang@huawei.com> wrote:
>> Hi All,
>>
>> The master branch on my overlayfs-progs [1] has been updated.
>>
>> No feature add, just handle comments form Amir in last iterations and
>> fix some bugs:
>> - Improve header comments for many functions, these becomes more readable.
>
> Looking very good!
> FYI the "header comment" which I requested, are the comment on the top of
> the file. But hey I'm not complaining ;-)
>
>> - Fix some path manipulation bugs in path.c.
>
> Sigh. Too bad you couldn't find a path manipulation library for joinpath()
> and basename2(). Things like that should really never be re-implemented.
> If you really have to implement them or really want to, then you should
> write simple unit tests that run on 'make test' to verify that your helpers
> do what you claim they do for all the listed inputs, because right now,
> I doubt that you have good test coverage for complex path composing
> just from running fsck.overlay itself.
>
Sorry, I didn't found such functions in C library (glibc), so have to re-implement it.
I have already test all listed inputs (not post it), maybe I can post it latter.
Thanks,
Yi.
>> - Improve impurities check.
>> - Split out functions and constants from kernel into overlayfs.c/.h.
>> - Update README, split out and detail TODO list.
>>
>
> Looks good!
>
> Amir.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
prev parent reply other threads:[~2018-02-01 4:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 10:23 [ANNOUNCE] fsck.overlayfs: update master branch zhangyi (F)
2018-01-31 20:23 ` Amir Goldstein
2018-02-01 4:16 ` zhangyi (F) [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=2b05eb7b-63f2-39c9-1009-7199e94de7fe@huawei.com \
--to=yi.zhang@huawei.com \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=miklos@szeredi.hu \
--cc=yangerkun@huawei.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