)]}'
{
  "commit": "09116a1c31e3754cb18bb69ef057342cd7808935",
  "tree": "cdfdb62eb8291aba5e274ca439b0647dee6295e5",
  "parents": [
    "5e1e6b93d024b5a01f4e957a2bedba899cb22f68"
  ],
  "author": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Nov 16 16:54:32 2011 -0800"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Nov 16 21:52:24 2011 -0800"
  },
  "message": "refs: loosen over-strict \"format\" check\n\nThe add_extra_ref() interface is used to add an extra-ref that is _not_\nour ref for the purpose of helping auto-following of tags and reducing\nobject transfer from remote repository, and they are typically formatted\nas a tagname followed by ^{} to make sure no valid refs match that\npattern. In other words, these entries are deliberately formatted not to\npass check-refname-format test.\n\nA recent series however added a test unconditionally to the add_ref()\nfunction that is called from add_extra_ref(). The check may be sensible\nfor other two callsites of the add_ref() interface, but definitely is\na wrong thing to do in add_extra_ref(). Disable it.\n\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\nAcked-by: Michael Haggerty \u003cmhagger@alum.mit.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e69ba26b74e430388c63af21473438468678bb4b",
      "old_mode": 33188,
      "old_path": "refs.c",
      "new_id": "e7843eb6b70b7de6c1ed1992db7adee1d99b27bc",
      "new_mode": 33188,
      "new_path": "refs.c"
    },
    {
      "type": "modify",
      "old_id": "895f5595aee9341276e79497b9c4a8736c78e5e7",
      "old_mode": 33261,
      "old_path": "t/t5700-clone-reference.sh",
      "new_id": "c4c375ac042bbb7f58998c87d8c9277d2f5004a6",
      "new_mode": 33261,
      "new_path": "t/t5700-clone-reference.sh"
    }
  ]
}