From: Hans-Peter Jansen <hpj@urpla.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org
Subject: Re: [GIT PULL] overlay filesystem fixes for 3.18
Date: Fri, 21 Nov 2014 12:32:54 +0100 [thread overview]
Message-ID: <1962959.JkOx4gJGaG@xrated> (raw)
In-Reply-To: <20141120164531.GB3596@tucsk>
Dear Miklos,
On Donnerstag, 20. November 2014 17:45:31 Miklos Szeredi wrote:
>
> The biggest change is to rename the filesystem from "overlayfs" to
> "overlay". This will allow legacy overlayfs to be easily carried by distros
> alongside the new mainline one.
Would you kindly give a firm elaboration of this rename?
Why would a distro kernel maintainer want to keep the external overlayfs
patches together with the now in kernel module?
Isn't it enough to drop the external patches from distro kernels in order to
use it successfully or are there any semantic changes hidden that an admin
should know about?
BTW: congrats to all involved parties. A layered filesystem finally arrived in
the Linux kernel! This is a quantum leap for creative system architects.
Cheers,
Pete
proud user of aufs (and formerly unionfs) based fat diskless systems since
about a decade.
next prev parent reply other threads:[~2014-11-21 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 16:45 [GIT PULL] overlay filesystem fixes for 3.18 Miklos Szeredi
2014-11-20 21:00 ` Al Viro
2014-11-21 10:43 ` Sedat Dilek
2014-11-21 10:50 ` Miklos Szeredi
2014-11-22 8:40 ` Sedat Dilek
2014-11-21 11:32 ` Hans-Peter Jansen [this message]
2014-11-21 12:41 ` Miklos Szeredi
2014-11-21 14:51 ` Hans-Peter Jansen
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=1962959.JkOx4gJGaG@xrated \
--to=hpj@urpla.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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