>>> On 30.11.15 at 16:42, <ian.jack...@eu.citrix.com> wrote:
> Doug Goldstein writes ("Re: [PATCHv6] 01/28] build: import Kbuild/Kconfig
> from Linux 4.2"):
>> The whole point here was to bring in the kconfig bits from Linux 4.2
>> untouched for traceability for where the code came from. By doing it
>> this way it allows Xen to rebase kconfig support to a newer version much
>> easier since its all self-contained.
>
> I think this is a very good point.
>
> 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?
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.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
