)]}'
{
  "commit": "0610c8a8a258e869a542e5fdb964c6816336559e",
  "tree": "d70e7aba355ec74c4310ac5f4cc57a8f713954ea",
  "parents": [
    "d1a1dc0be866219f7a613c6368c6a036b8eefe03"
  ],
  "author": {
    "name": "Dave Hansen",
    "email": "dave@linux.vnet.ibm.com",
    "time": "Mon Jul 01 13:04:43 2013 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Thu Jul 04 11:25:39 2013 -0700"
  },
  "message": "order memory debugging Kconfig options\n\nOriginal posting:\n\n\thttp://lkml.kernel.org/r/20121214184203.37E6C724@kernel.stglabs.ibm.com\n\nThere are a *LOT* of memory debugging options.  They are just scattered\nall over the \"Kernel Hacking\" menu.  Sure, \"memory debugging\" is a very\nvague term and it\u0027s going to be hard to make absolute rules about what\ngoes in here, but this has to be better than what we had before.\n\nThis does, however, leave out the architecture-specific memory\ndebugging options (like x86\u0027s DEBUG_SET_MODULE_RONX).  There would need\nto be some substantial changes to move those in here.  Kconfig can not\neasily mix arch-specific and generic options together: it really\nrequires a file per-architecture, and I think having an\narch/foo/Kconfig.debug-memory might be taking things a bit too far\n\nSigned-off-by: Dave Hansen \u003cdave@linux.vnet.ibm.com\u003e\nSigned-off-by: Dave Hansen \u003cdave.hansen@linux.intel.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cc443bc6edfc83f7d85b56a904a7093b27e55598",
      "old_mode": 33188,
      "old_path": "lib/Kconfig.debug",
      "new_id": "57e18ac6ca3c88a872a257f3b343515ef17e61cd",
      "new_mode": 33188,
      "new_path": "lib/Kconfig.debug"
    }
  ]
}