From: Andrew Watts <akwatts@ymail.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [overlayfs/port] overlayfs: v13 port attempt to kernel 3.5
Date: Thu, 16 Aug 2012 20:05:21 -0500 [thread overview]
Message-ID: <20120817010519.GA2440@ymail.com> (raw)
In-Reply-To: <CA+icZUX+4mMYqNn5_5EKXTdqbZ25K1HFbsRR5TrToaGJaSPttw@mail.gmail.com>
On Thu, Aug 16, 2012 at 11:14:26PM +0200, Sedat Dilek wrote:
> Might be easier to collect/extract commits listed in [1]?
>
> If you are on Ubuntu: Check mainline kernels in [2] (quantal) and [3] (precise).
>
> - Sedat -
>
That indeed was much easier and I have it working great on 3.5.2. Many
thanks for the link to the git repo.
It would be nice to see overlayfs ack'd into mainline at some point. Is
there any chance of this?
~ Andy
next prev parent reply other threads:[~2012-08-17 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 20:44 [overlayfs/port] overlayfs: v13 port attempt to kernel 3.5 Andrew Watts
2012-08-16 21:14 ` Sedat Dilek
2012-08-17 1:05 ` Andrew Watts [this message]
2012-08-17 9:18 ` Sedat Dilek
2012-08-20 10:38 ` J. R. Okajima
2012-08-20 11:26 ` Sedat Dilek
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=20120817010519.GA2440@ymail.com \
--to=akwatts@ymail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sedat.dilek@gmail.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).