)]}'
{
  "log": [
    {
      "commit": "a192a8ced65ceea8bfe44f0eac6a394cbf80d936",
      "tree": "e8188ef2b11a50e0052cb7af40749fadad32dcea",
      "parents": [
        "51d34bf06aa67ab5b29c5541e777505ad37907d0"
      ],
      "author": {
        "name": "Roozbeh Pournader",
        "email": "roozbeh@google.com",
        "time": "Tue Jan 10 15:24:32 2017 -0800"
      },
      "committer": {
        "name": "Roozbeh Pournader",
        "email": "roozbeh@google.com",
        "time": "Wed Jan 11 15:52:08 2017 -0800"
      },
      "message": "Treat Latin American locales specially\n\nDue to legacy reasons, Android translations of European Spanish were\nkept under \u0027es\u0027, while Latin American Spanish translations were kept\nunder \u0027es-US\u0027. The combination of this, and the new locale\npreference rules in Nougat, resulted in \u0027es\u0027 winning over \u0027es-US\u0027 for\nall Latin American locales, since \u0027es\u0027 was a direct ancestor, while\n\u0027es-US\u0027 was just a fallback.\n\nThe changes in Nougat had assumed that app developers would put Latin\nAmerican Spanish translations under \u0027es-419\u0027, but that could create a\nbackward-compatibility problem under older Android versions that did\nnot support three-digit region codes properly.\n\nThis CL keeps the Nougat logic and its locale parent tree, but\nspecial-cases es-US and es-MX to be treated as equivalents of es-419\nin cases where they are present and es-419 is not.\n\nBug: 31545805\nBug: 34126460\nTest: unit tests are included\nChange-Id: Iab26f41294587ee044685a5a6560520c7cbb06f7\n"
    },
    {
      "commit": "27953c349fa1c46698f57ae5f26339560c21adac",
      "tree": "e6be55731d70f74688c8ba84c91fd31d7901cc0b",
      "parents": [
        "c92035b1aa2b064d97377795553c11261f7e7cce"
      ],
      "author": {
        "name": "Roozbeh Pournader",
        "email": "roozbeh@google.com",
        "time": "Mon Feb 01 13:49:52 2016 -0800"
      },
      "committer": {
        "name": "Roozbeh Pournader",
        "email": "roozbeh@google.com",
        "time": "Mon Feb 01 14:56:52 2016 -0800"
      },
      "message": "Make default resources a better match for en-US requests\n\nWhen locale fallback landed, resources which specified an \u0027English\u0027\nlocale started to be considered a better match for en-US, even though\ntraditionally, apps tend to ship US English resources under their\ndefault locale.\n\nThis fixes that, and makes en-US requests match default locales.\n\nBug: 26756573\nBug: 26789680\nBug: 26803868\nChange-Id: I460c276bfc6ddba0439dcdf87497a0aece0fa05d\n"
    },
    {
      "commit": "b927c559e1ef8530b08712507f320502627db298",
      "tree": "f0d2fd051cb4486239e6f6187e0da53e416fdaeb",
      "parents": [
        "ac3e599069e1b87ea190f008aef60a506c8561c7"
      ],
      "author": {
        "name": "Roozbeh Pournader",
        "email": "roozbeh@google.com",
        "time": "Fri Jan 15 11:23:42 2016 -0800"
      },
      "committer": {
        "name": "Roozbeh Pournader",
        "email": "roozbeh@google.com",
        "time": "Thu Jan 21 13:47:22 2016 -0800"
      },
      "message": "Implement smarter locale resource selection\n\n* Add support for determining script from language and region.\n* Add support for determining special parents of locales.\n* Add support for smart comparison of locales with only a difference\n  in region, using the locale parentage tree.\n* Fix LocaleData.matchScore() to not fallback to old locale matching\n  behavior if we can\u0027t determine a script.\n* Allow four-character variant codes. (Previously, only five- to\n  eight-character variant codes were allowed.)\n\nBug: 7296673\nBug: 26589793\nChange-Id: Ibde0a48c0564ff383b41068095a5cbacfe7b94bc\n"
    }
  ]
}