From: Linus Torvalds <torvalds@linux-foundation.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-unionfs@vger.kernel.org
Subject: Re: [GIT PULL] overlayfs fixes for 4.9-rc3
Date: Fri, 4 Nov 2016 20:06:02 -0700 [thread overview]
Message-ID: <CA+55aFx7bsMNKMfxaxXuw=E13H5dQpGQHdNgBKKt_JKyL2eGeQ@mail.gmail.com> (raw)
In-Reply-To: <20161104093050.GB1839@veci.piliscsaba.szeredi.hu>
On Fri, Nov 4, 2016 at 2:30 AM, Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> Also introduce the concept of feature flags to allow backward incompatible
> changes to the overlay format. This should have been there from day one; the
> best we can do now is backport to stable kernels. Add the check for features
> without adding any actual features yet.
No. I pulled the three other commits, but not that last one.
That feature just seems to actively *encourage* backwards incompatible
features. It's a bad idea. Don't do it. If we've been able to do
without it so far, then why should we suddenly start doing things like
this?
So I don't agree that it should have been there since day one, it just
shouldn't exist at all.
Linus
next prev parent reply other threads:[~2016-11-05 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 9:30 [GIT PULL] overlayfs fixes for 4.9-rc3 Miklos Szeredi
2016-11-05 3:06 ` Linus Torvalds [this message]
2016-11-05 6:44 ` Amir Goldstein
2016-11-05 17:41 ` Linus Torvalds
2016-11-05 19:45 ` Miklos Szeredi
2016-11-05 21:30 ` Linus Torvalds
2016-11-05 21:41 ` Peter Rosin
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='CA+55aFx7bsMNKMfxaxXuw=E13H5dQpGQHdNgBKKt_JKyL2eGeQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).