Re: [Xen-devel] [PATCHv6] 01/28] build: import Kbuild/Kconfig from Linux 4.2

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

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.

Something like

  Import scripts/kconfig from Linux 4.2.0 commit id abcdefgh into our
  own xen/scripts/kconfig.  So far, these are unused - they will be
  wired into our own build system shortly.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel