)]}'
{
  "commit": "0f0625a630081d532d528d87ba236a6385bbbac1",
  "tree": "e6c3e6c57219732b8165105970590a7d09cec91d",
  "parents": [
    "fb4175b0e4bec59b97dae84a0073d8a5334508d6",
    "ff165f00c1065d94c0bcab8708364e6dc5655f5d"
  ],
  "author": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Mar 26 17:11:21 2020 -0700"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Thu Mar 26 17:11:21 2020 -0700"
  },
  "message": "Merge branch \u0027jc/describe-misnamed-annotated-tag\u0027\n\nWhen \"git describe C\" finds an annotated tag with tagname A to be\nthe best name to explain commit C, and the tag is stored in a\n\"wrong\" place in the refs/tags hierarchy, e.g. refs/tags/B, the\ncommand gave a warning message but used A (not B) to describe C.\nIf C is exactly at the tag, the describe output would be \"A\", but\n\"git rev-parse A^0\" would not be equal as \"git rev-parse C^0\".  The\nbehavior of the command has been changed to use the \"long\" form\ni.e. A-0-gOBJECTNAME, which is correctly interpreted by rev-parse.\n\n* jc/describe-misnamed-annotated-tag:\n  describe: force long format for a name based on a mislocated tag\n",
  "tree_diff": []
}