)]}'
{
  "commit": "dc7ace5f776f30fe4e10d8a3fa8146ad21893544",
  "tree": "3e9960809dfb4af337f22b13796846d940c6792f",
  "parents": [
    "ac5fc1c57f2a964e1b5480a25b6fd447ab18b9b9"
  ],
  "author": {
    "name": "Stefano Lattarini",
    "email": "stefano.lattarini@gmail.com",
    "time": "Thu Jul 19 09:50:01 2012 +0200"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Jul 19 10:30:26 2012 -0700"
  },
  "message": "build: \"make clean\" should not remove configure-generated files\n\nThose filed hold variables, settings and information set by the\nconfiguration process run by \u0027./configure\u0027; in Autotools-based\nbuild system that kind of stuff should only be removed by\n\"make distclean\".  Having it removed by \"make clean\" is not only\ninconsistent, but causes real confusion for that part of the Git\naudience that is used to the Autotools semantics; for example,\nan autotools old-timer that has run:\n\n    ./configure --prefix /opt/git\n\nin the past, without running \"make distclean\" afterwards, would\nexpect a \"make install\" issued after a \"make clean\" to rebuild and\ninstall git in \u0027/opt/git\u0027; but with the current behaviour, the\n\"make clean\" invocation removes (among the other things) the file\n\u0027config.mak.autogen\u0027, so that the \"make install\" falls back to the\ndefault prefix of \u0027$HOME\u0027, thus installing git in the user\u0027s home\ndirectory -- definitely unexpected.\n\nSigned-off-by: Stefano Lattarini \u003cstefano.lattarini@gmail.com\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "285c660e1454ad3b591660907226fb5b89a3cf4e",
      "old_mode": 33188,
      "old_path": "Makefile",
      "new_id": "88a76a398ce74cc4cf9e2821118d15a50532552e",
      "new_mode": 33188,
      "new_path": "Makefile"
    }
  ]
}