)]}'
{
  "commit": "d773c6314d5660266313772b3fd8a466c3dbc559",
  "tree": "39b835c06f96d6ffa7d03bb860cadc4d55923f66",
  "parents": [
    "1db4a75c8d18d8827ac710e87219b349558d9196"
  ],
  "author": {
    "name": "SZEDER Gábor",
    "email": "szeder@ira.uka.de",
    "time": "Tue Jul 08 18:56:14 2008 +0200"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Tue Jul 08 16:35:05 2008 -0700"
  },
  "message": "bash: offer only paths after \u0027--\u0027\n\nMany git commands use \u0027--\u0027 to separate subcommands, options, and refs\nfrom paths.  However, the programmable completion for several of these\ncommands does not respect the \u0027--\u0027, and offer subcommands, options, or\nrefs after a \u0027--\u0027, although only paths are permitted.  e.g. \u0027git bisect\n-- \u003cTAB\u003e\u0027 offers subcommands, \u0027git log -- --\u003cTAB\u003e\u0027 offers options and\n\u0027git log -- git\u003cTAB\u003e\u0027 offers all gitgui tags.\n\nThe completion for the following commands share this wrong behaviour:\n  am add bisect commit diff log reset shortlog submodule gitk.\n\nTo avoid this, we check the presence of a \u0027--\u0027 on the command line first\nand let the shell do filename completion, if one is found.\n\nSigned-off-by: SZEDER Gábor \u003cszeder@ira.uka.de\u003e\nAcked-by: Shawn O. Pearce \u003cspearce@spearce.org\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0eb8df020be3c6dd0e701428a6335316aa608b6a",
      "old_mode": 33261,
      "old_path": "contrib/completion/git-completion.bash",
      "new_id": "cff28a88afe3262705acc3d9b47e97be65dbb8d1",
      "new_mode": 33261,
      "new_path": "contrib/completion/git-completion.bash"
    }
  ]
}