)]}'
{
  "commit": "0259c3f76d4928383f46628f41c9613d07b64b7d",
  "tree": "c1d04094790333db4cb1569ce62c9de82ee0be09",
  "parents": [
    "5295e8364332db77d75fce11f1d19c053919a9c9"
  ],
  "author": {
    "name": "Paul M Furley",
    "email": "paul@paulfurley.com",
    "time": "Thu Sep 27 17:22:31 2018 +0000"
  },
  "committer": {
    "name": "Filippo Valsorda",
    "email": "filippo@golang.org",
    "time": "Mon Oct 01 20:26:45 2018 +0000"
  },
  "message": "openpgp: use latest subkey binding signature\n\nRather than using the first subkey binding signature encountered, use\nthe one with the most recent creation data, as per the recommendation from\nRFC 4880:\n\n\u003e An implementation that encounters multiple self-signatures on the\n\u003e same object may resolve the ambiguity in any way it sees fit, but it\n\u003e is RECOMMENDED that priority be given to the most recent self-\n\u003e signature.\n\nThis allows subkeys to approach expiry then be re-signed with a new expiry.\n\nThis extends the recent commit 0e37d00 by @aviau and @FiloSottile.\n\nFixes golang/go#26468\n\nChange-Id: I7f12706727373259c188bfee4254306ef9d4e935\nGitHub-Last-Rev: 0da814166411a3c3334312576d3f7f8f2bba4ff4\nGitHub-Pull-Request: golang/crypto#57\nReviewed-on: https://go-review.googlesource.com/135357\nReviewed-by: Filippo Valsorda \u003cfilippo@golang.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d8b896d85df64efd66a55a1a23eb47297af13205",
      "old_mode": 33188,
      "old_path": "openpgp/keys.go",
      "new_id": "3e2518600e29e9e736125ed119cd5ea0bc99539c",
      "new_mode": 33188,
      "new_path": "openpgp/keys.go"
    }
  ]
}