)]}'
{
  "commit": "b2670eacfb013169b8bf151a5078a9ef8ef86466",
  "tree": "81541b003f9853b2bcf5e4f1e4f4b340d9d029ac",
  "parents": [
    "493e3758be1d5628b4d799fe21d68969edbe32aa"
  ],
  "author": {
    "name": "Paolo \u0027Blaisorblade\u0027 Giarrusso",
    "email": "blaisorblade@yahoo.it",
    "time": "Thu Oct 19 23:28:23 2006 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@g5.osdl.org",
    "time": "Fri Oct 20 10:26:36 2006 -0700"
  },
  "message": "[PATCH] uml: use DEFCONFIG_LIST to avoid reading host\u0027s config\n\nThis should make sure that, for UML, host\u0027s configuration files are not\nconsidered, which avoids various pains to the user.  Our dependency are such\nthat the obtained Kconfig will be valid and will lead to successful\ncompilation - however they cannot prevent an user from disabling any boot\ndevice, and if an option is not set in the read .config (say\n/boot/config-XXX), with make menuconfig ARCH\u003dum, it is not set.  This always\ndisables UBD and all console I/O channels, which leads to non-working UML\nkernels, so this bothers users - especially now, since it will happen on\nalmost every machine (/boot/config-`uname -r` exists almost on every machine).\n It can be workarounded with make defconfig ARCH\u003dum, but it is non-obvious and\ncan be avoided, so please _do_ merge this patch.\n\nGiven the existence of options, it could be interesting to implement\n(additionally) \"option required\" - with it, Kconfig will refuse reading a\n.config file (from wherever it comes) if the given option is not set.  With\nthis, one could mark with it the option characteristic of the given\narchitecture (it was an old proposal of Roman Zippel, when I pointed out our\nproblem):\n\nconfig UML\n\toption required\n\tdefault y\n\nHowever this should be further discussed:\n*) for x86, it must support constructs like:\n\n\u003d\u003darch/i386/Kconfig\u003d\u003d\nconfig 64BIT\n\toption required\n\tdefault n\nwhere Kconfig must require that CONFIG_64BIT is disabled or not present in the\nread .config.\n\n*) do we want to do such checks only for the starting defconfig or also for\n   .config? Which leads to:\n*) I may want to port a x86_64 .config to x86 and viceversa, or even among more\n   different archs. Should that be allowed, and in which measure (the user may\n   force skipping the check for a .config or it is only given a warning by\n   default)?\n\nCc: Roman Zippel \u003czippel@linux-m68k.org\u003e\nCc: \u003ckbuild-devel@lists.sourceforge.net\u003e\nSigned-off-by: Paolo \u0027Blaisorblade\u0027 Giarrusso \u003cblaisorblade@yahoo.it\u003e\nCc: Jeff Dike \u003cjdike@addtoit.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "50fb89e3d95dbb7a299ef3fa4eb5ed4f06b1c906",
      "old_mode": 33188,
      "old_path": "arch/um/Kconfig",
      "new_id": "5ac1f2963ae383e391cb601c730ed645e0707b6a",
      "new_mode": 33188,
      "new_path": "arch/um/Kconfig"
    },
    {
      "type": "modify",
      "old_id": "10382931eead561940c023bd1b376863b9b11dab",
      "old_mode": 33188,
      "old_path": "init/Kconfig",
      "new_id": "c8b2624af1767398632f68825014c825fbb7fe8e",
      "new_mode": 33188,
      "new_path": "init/Kconfig"
    }
  ]
}