From: Amir Goldstein <amir73il@gmail.com>
To: Vyacheslav Yurkov <uvv.mail@gmail.com>
Cc: fstests@vger.kernel.org, Zorro Lang <zlang@kernel.org>,
linux-unionfs@vger.kernel.org,
Gao Xiang <hsiangkao@linux.alibaba.com>,
Jingbo Xu <jefflexu@linux.alibaba.com>,
"zhangyi (F)" <yi.zhang@huawei.com>
Subject: Re: [PATCH] README: Update overlayfs URL
Date: Sun, 1 Oct 2023 15:42:17 +0300 [thread overview]
Message-ID: <CAOQ4uxjawFZv_6NGKvmiVBfAL2eqExwXhunf=C-_yL3eAcD_gA@mail.gmail.com> (raw)
In-Reply-To: <9e57cce1-2eca-411d-98a4-3321823d8f3d@gmail.com>
On Sun, Oct 1, 2023 at 3:41 AM Vyacheslav Yurkov <uvv.mail@gmail.com> wrote:
>
> On 29.09.2023 05:16, Amir Goldstein wrote:
> > On Thu, Sep 28, 2023 at 11:30 PM Vyacheslav Yurkov <uvv.mail@gmail.com> wrote:
> >> Overlayfs-tools and overlayfs-progs projects have been merged together.
> >>
> > Nice :)
> >
> > Do you also have any plans to improve the tools?
>
> Thanks for the review!
> I'll move the instructions completely to README.overlay in V2 then. Is
> there a particular reason that the file starts from an empty line?
No reason.
> (perhaps I could remove that as well in the same patch)
>
OK.
> Right now the plan was only to maintain both projects and accept patches
> from others. Perhaps I will also update the build system to something
> up-to-date. As for further development, unfortunately I don't have a
> project behind ATM to improve the tools further. If something pops up
> (or you have something), I could try to find a capacity for that.
Gao was asking about an offline merge tool, so I pointed him
at overlayfs-tools:
https://lore.kernel.org/linux-unionfs/bc9b3731-9eac-28be-e635-44a098e87d76@linux.alibaba.com/
Maybe he can explain what features in specific he was looking for.
Thanks,
Amir.
prev parent reply other threads:[~2023-10-01 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 20:28 [PATCH] README: Update overlayfs URL Vyacheslav Yurkov
2023-09-29 3:16 ` Amir Goldstein
2023-10-01 0:41 ` Vyacheslav Yurkov
2023-10-01 12:42 ` Amir Goldstein [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='CAOQ4uxjawFZv_6NGKvmiVBfAL2eqExwXhunf=C-_yL3eAcD_gA@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=uvv.mail@gmail.com \
--cc=yi.zhang@huawei.com \
--cc=zlang@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).