linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: cgxu519@zoho.com.cn
Cc: linux-unionfs <linux-unionfs@vger.kernel.org>
Subject: Re: syncfs improvement for overlayfs
Date: Fri, 24 Jan 2020 15:21:38 +0100	[thread overview]
Message-ID: <CAJfpegv949oJAZQNjTsq5MQHz6LLkfihp4S_mWRuYsLRuPCgFg@mail.gmail.com> (raw)
In-Reply-To: <16d7200e45c.1398c37e020790.5506577327176178828@zoho.com.cn>

On Fri, Sep 27, 2019 at 11:15 AM admin <cgxu519@zoho.com.cn> wrote:
>
> Hi Miklos,
>
> It's been a while since I posted my last version of syncfs improvement patch[1]
> and I noticed it isn't get merged yet. If you think this patch is still valuable then
> I would like to do rebase on latest overlayfs tree and resend for review.
> What do you think?


Hi,

Sorry, this has fallen off my radar.  Can you please rebase and resend?

Thanks,
Miklos

  reply	other threads:[~2020-01-24 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27  9:15 syncfs improvement for overlayfs admin
2020-01-24 14:21 ` Miklos Szeredi [this message]
2020-01-30  3:17   ` admin

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=CAJfpegv949oJAZQNjTsq5MQHz6LLkfihp4S_mWRuYsLRuPCgFg@mail.gmail.com \
    --to=miklos@szeredi.hu \
    --cc=cgxu519@zoho.com.cn \
    --cc=linux-unionfs@vger.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 NNTP newsgroup(s).