)]}'
{
  "commit": "0df670bc0b8b5499859829ba0889ce96a75304a6",
  "tree": "e95738e380852775d16806643a57ece2d4d39461",
  "parents": [
    "7364aee138326303371c1a17d3259912366c1b55",
    "f24c30e0b6b13078d8fc7cd71b9989d28fd76610"
  ],
  "author": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Sep 09 13:53:08 2020 -0700"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Wed Sep 09 13:53:09 2020 -0700"
  },
  "message": "Merge branch \u0027jt/interpret-branch-name-fallback\u0027\n\n\"git status\" has trouble showing where it came from by interpreting\nreflog entries that recordcertain events, e.g. \"checkout @{u}\", and\ngives a hard/fatal error.  Even though it inherently is impossible\nto give a correct answer because the reflog entries lose some\ninformation (e.g. \"@{u}\" does not record what branch the user was\non hence which branch \u0027the upstream\u0027 needs to be computed, and even\nif the record were available, the relationship between branches may\nhave changed), at least hide the error to allow \"status\" show its\noutput.\n\n* jt/interpret-branch-name-fallback:\n  wt-status: tolerate dangling marks\n  refs: move dwim_ref() to header file\n  sha1-name: replace unsigned int with option struct\n",
  "tree_diff": []
}