Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755724AbaKUMmD (ORCPT ); Fri, 21 Nov 2014 07:42:03 -0500 Received: from mail-qc0-f175.google.com ([209.85.216.175]:35188 "EHLO mail-qc0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751368AbaKUMl6 (ORCPT ); Fri, 21 Nov 2014 07:41:58 -0500 MIME-Version: 1.0 X-Originating-IP: [46.139.80.5] In-Reply-To: <1962959.JkOx4gJGaG@xrated> References: <20141120164531.GB3596@tucsk> <1962959.JkOx4gJGaG@xrated> Date: Fri, 21 Nov 2014 13:41:57 +0100 Message-ID: Subject: Re: [GIT PULL] overlay filesystem fixes for 3.18 From: Miklos Szeredi To: Hans-Peter Jansen Cc: Al Viro , Linus Torvalds , Linux-Fsdevel , Kernel Mailing List , linux-unionfs@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 21, 2014 at 12:32 PM, Hans-Peter Jansen wrote: > 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? See this thread: https://lkml.org/lkml/2014/11/18/433 Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/