From: Ritesh Harjani <riteshh@linux.ibm.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Chengguang Xu <cgxu519@mykernel.net>,
Miklos Szeredi <miklos@szeredi.hu>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: Getting WIP aops branch(ovl-aops-wip) in shape for merging.
Date: Wed, 26 Aug 2020 19:57:12 +0530 [thread overview]
Message-ID: <20200826142714.2CA0FAE067@d06av26.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <CAOQ4uxj7JzmKdrV5Z2AHFFk09OwJL_djjE=JOxVOxQU8HVFkVg@mail.gmail.com>
Hello Amir,
On 8/12/20 10:44 PM, Amir Goldstein wrote:
>> Sure. So here is what I was planning.
>> I am about to start going over patches mentioned in Amir's ovl-aops-wip
>> branch. My first preference would be to port it to latest upstream and
>> start cleaning it up.
>> I will update the branch details once those patches are ported to
>> latest upstream. Let me know if we should do this in any different way.
>>
>
> Sounds like a plan.
>
>> I will also be joining this year's plumber, in case if we want
>> to discuss anything on this. Although I am not sure if by then, I would
>> be able to get any substantial work done to discuss with a wider
>> audience. But nevertheless, we can always have a call/email exchanges
>> for this, both before and after the conference :)
>>
>
> Nice. I will be giving a talk on new overlayfs features on the containers track.
> I guess there won't be much in the hallway tracks this year...
I went over almost all patches which you have in ovl-aops-wip branch.
For now I have only ported some of the straight forward patches,
since I had few queries on those other patches and one was mainly
w.r.t. metadata only feature functionality.
Do you have sometime today to discuss about it in any of the LPC hacker
room? I was thinking maybe discussing this in person will help a lot.
Any preferred slot? I could not find you online on LPC chat area,
we can as well discuss the slot there. But I am fine with any of the LPC
timings.
-ritesh
next prev parent reply other threads:[~2020-08-26 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200313140843.5C65542045@d06av24.portsmouth.uk.ibm.com>
[not found] ` <CAOQ4uxgabS0GMaMXHbhXoBv9OXAZv9O2WzZ-h9aWhZm6quASOg@mail.gmail.com>
[not found] ` <20200812140012.875A711C089@d06av25.portsmouth.uk.ibm.com>
[not found] ` <CAOQ4uxhf6R2Gr1wV_LGbAuDGuuPmnb0Mvx43MxWc2O1gQkrGUQ@mail.gmail.com>
2020-08-12 17:00 ` Getting WIP aops branch(ovl-aops-wip) in shape for merging Ritesh Harjani
2020-08-12 17:14 ` Amir Goldstein
2020-08-12 17:30 ` Ritesh Harjani
2020-08-26 14:27 ` Ritesh Harjani [this message]
2020-08-27 6:42 ` Amir Goldstein
2020-08-27 7:36 ` Ritesh Harjani
[not found] ` <1742eff988b.f97421f5734.6795211467293709335@mykernel.net>
2020-08-27 8:25 ` Ritesh Harjani
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=20200826142714.2CA0FAE067@d06av26.portsmouth.uk.ibm.com \
--to=riteshh@linux.ibm.com \
--cc=amir73il@gmail.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=cgxu519@mykernel.net \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).