linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Ritesh Harjani <riteshh@linux.ibm.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>,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: Getting WIP aops branch(ovl-aops-wip) in shape for merging.
Date: Thu, 27 Aug 2020 09:42:16 +0300	[thread overview]
Message-ID: <CAOQ4uxjCPQF4LxE4kmMuOf3sa7Xrkcm-ZvdjBBtKgNWjY7Qb6g@mail.gmail.com> (raw)
In-Reply-To: <20200826142714.2CA0FAE067@d06av26.portsmouth.uk.ibm.com>

On Wed, Aug 26, 2020 at 5:27 PM Ritesh Harjani <riteshh@linux.ibm.com> wrote:
>
> 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.
>

Those questions you can also ask Vivek if you find him in LPC...

> 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.
>

I agree that a video meetup can be useful to kickoff this effort, but
it is preferred if Chengguang can also attend, because it feels like
you guys need to collaborate.

> 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.
>

I cannot do LPC times today or tomorrow, but the hacker rooms are
open and judging by the time of your email you may be closer to my
time zone, so if you want to schedule a meeting somewhere in the next
5 hours, I can join. (7:00-12:00 UTC).

Otherwise, we can always schedule a call outside of LPC, where
participants not registered to LPC will be able to join (Chengguang?).

Thanks,
Amir.

  reply	other threads:[~2020-08-27  6:42 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
2020-08-27  6:42             ` Amir Goldstein [this message]
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=CAOQ4uxjCPQF4LxE4kmMuOf3sa7Xrkcm-ZvdjBBtKgNWjY7Qb6g@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=cgxu519@mykernel.net \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=riteshh@linux.ibm.com \
    --cc=vgoyal@redhat.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).