)]}'
{
  "commit": "e93bc1a0cab3e54e3c1947e01c8e73892e35630d",
  "tree": "f7b40bb868ad3a4e1895a5a0cca82a5c08300c2a",
  "parents": [
    "a6c366324cacd5f71107dd01362b995a1c67b1ad"
  ],
  "author": {
    "name": "Michal Marek",
    "email": "mmarek@suse.cz",
    "time": "Mon Mar 08 10:26:22 2010 +0100"
  },
  "committer": {
    "name": "Michal Marek",
    "email": "mmarek@suse.cz",
    "time": "Mon Mar 08 10:26:22 2010 +0100"
  },
  "message": "Revert \"kbuild: specify absolute paths for cscope\"\n\nThis reverts commit eb8f844c0a41c4529a7d06b7801296eca9ae67aa. Ian\nCampbell writes:\n\u003e I keep my kernel source tree on a more powerful build box where I run my\n\u003e builds etc (including \"make cscope\") but run my editor from my\n\u003e workstation with an NFS mount to the source. This worked fine for me\n\u003e using relative paths for cscope. Using absolute paths in cscope breaks\n\u003e this previously working setup because the root path is not the same on\n\u003e both systems. I guess this is similar to moving the source tree around.\n\u003e\n\u003e Without wanting to start a flamewar it really sounds to me like we are\n\u003e working around a vim (or cscope) bug here, emacs with cscope bindings\n\u003e works fine in this configuration.\n\nGiven that absolute paths can be forced by make O\u003d. cscope, change the\ndefault back to relative paths.\n\nIan Campbell \u003cijc@hellion.org.uk\u003e\nCc: Daniel Vetter \u003cdaniel.vetter@ffwll.ch\u003e\nSigned-off-by: Michal Marek \u003cmmarek@suse.cz\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "868b4c8fc25f563f179abf4bbd75d8caeb633d07",
      "old_mode": 33261,
      "old_path": "scripts/tags.sh",
      "new_id": "8509bb51293530fae488f60594199031cd16bf07",
      "new_mode": 33261,
      "new_path": "scripts/tags.sh"
    }
  ]
}