)]}'
{
  "commit": "ffd1ac5dde053e861ad249d7d8d27df7cef56eb9",
  "tree": "25046d2a1da5054134d78e4b7eac9d206e2d5bfd",
  "parents": [
    "65a0cfc82a75146113b9e138cb9fdd5f04c018d0"
  ],
  "author": {
    "name": "Thomas Wolf",
    "email": "thomas.wolf@paranor.ch",
    "time": "Sun Aug 19 20:43:50 2018 +0200"
  },
  "committer": {
    "name": "Thomas Wolf",
    "email": "thomas.wolf@paranor.ch",
    "time": "Wed Aug 22 11:09:01 2018 +0200"
  },
  "message": "Fix fetching with duplicate ref updates\n\nIf packed refs are used, duplicate updates result in an exception\nbecause JGit tries to lock the same lock file twice. With non-atomic\nref updates, this used to work, since the same ref would simply be\nlocked and updated twice in succession.\n\nLet\u0027s be more lenient in this case and remove duplicates before\ntrying to do the ref updates. Silently skip duplicate updates\nfor the same ref, if they both would update the ref to the same\nobject ID. (If they don\u0027t, behavior is undefined anyway, and we\nstill throw an exception.)\n\nAdd a test that results in a duplicate ref update for a tag.\n\nBug: 529400\nChange-Id: Ide97f20b219646ac24c22e28de0c194a29cb62a5\nSigned-off-by: Thomas Wolf \u003cthomas.wolf@paranor.ch\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0622851822ea3cb5cc3a867e1d55e54d219bf713",
      "old_mode": 33188,
      "old_path": "org.eclipse.jgit.test/tst/org/eclipse/jgit/api/FetchCommandTest.java",
      "new_id": "530fb1b2fea572bdf07aebe8f1e892eabf638d8f",
      "new_mode": 33188,
      "new_path": "org.eclipse.jgit.test/tst/org/eclipse/jgit/api/FetchCommandTest.java"
    },
    {
      "type": "modify",
      "old_id": "39f0eea274aadb3bd94170e0df8d3a72185f1bfd",
      "old_mode": 33188,
      "old_path": "org.eclipse.jgit/src/org/eclipse/jgit/transport/FetchProcess.java",
      "new_id": "ed10f449dfff0675a4b552625df8704f3301bd3a",
      "new_mode": 33188,
      "new_path": "org.eclipse.jgit/src/org/eclipse/jgit/transport/FetchProcess.java"
    }
  ]
}