From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCHv6] 01/28] build: import Kbuild/Kconfig from
 Linux 4.2
Date: Mon, 30 Nov 2015 17:16:59 +0000
Message-ID: <22108.33931.22008.162522@mariner.uk.xensource.com>
References: <1448387538-12208-1-git-send-email-cardoe@cardoe.com>
	<1448387538-12208-2-git-send-email-cardoe@cardoe.com>
	<565C645C02000078000BA3AD@prv-mh.provo.novell.com>
	<565C6C7B.4060600@cardoe.com>
	<22108.28242.983982.939049@mariner.uk.xensource.com>
	<565C8F7702000078000BA686@prv-mh.provo.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <565C8F7702000078000BA686@prv-mh.provo.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>, Tim Deegan <tim@xen.org>, Doug Goldstein <cardoe@cardoe.com>, Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

Jan Beulich writes ("Re: [PATCHv6] 01/28] build: import Kbuild/Kconfig from Linux 4.2"):
> On 30.11.15 at 16:42, <Ian.Jackson@eu.citrix.com> wrote:
> > I would go further than this, and wholesale import the relevant files
> > into a subdirectory in a single commit that contains nothing else, and
> > mention the specific git commit id and version number in the Linux
> > tree in the commit message.
> 
> But what's the point of importing things we're not going to use?

I thought I had explained that.

A future re-import or merge will be much simpler if this import is a
simple wholesale copy of a directory or two or a simple glob pattern.

The runes used to do the import could be in the commit message for
easy reproduction.

> Imo such an import should be limited to those files that (later on)
> would actually get wired up. Hence the request to do a minimalistic
> import for this first round.

This would involve a series of piece-by-piece imports.  Any future
merge or re-import would involve retracing and re-executing those
steps.

It appears that we do disagree.  Perhaps the basic thing is: I don't
think we want to fork this code.  We want to be a downstream of Linux
for it.  If necessary we may edit, to an extent, the parts we import,
but hopefully we'll keep that to a minimum.

Ian.