)]}'
{
  "commit": "dcfbbd71affc6fb9cb360d7f88c0a7f260dd4abd",
  "tree": "a71f509cf81467016f9ba9ca8167242573c1cf8a",
  "parents": [
    "0d5a7503fecbc2fb68a914c9250d0f8fe731275c"
  ],
  "author": {
    "name": "Hannes Winkler",
    "email": "hanneswinkler2000@web.de",
    "time": "Tue Dec 17 19:09:06 2024 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Dec 17 18:09:06 2024 +0000"
  },
  "message": "embedder: fix bit-order in software pixel format description (#57156)\n\nThe order of the components for packed software pixel formats is incorrectly documented as being the order in the native type, least-significant-bit first. In reality it\u0027s the other way around. For example, for `RGB565`, the `R` is the 5 most significant bits in the 2-byte pixel value, rather than the least significant bits. The test even verify it is that way:\r\n\r\nhttps://github.com/flutter/engine/blob/main/shell/platform/embedder/tests/embedder_unittests.cc#L2782-L2785\r\n\r\nI assume noone used the software pixel formats until @sodiboo did, that\u0027s why it\u0027s gone unnoticed for so long.\r\n\r\nAlso contains some other minor documentation improvements.\r\n\r\n- Issue: https://github.com/flutter/flutter/issues/160149\r\n\r\n[C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4b880a6855d93a9f19c8b2e6fbfbbf22f6f15859",
      "old_mode": 33188,
      "old_path": "shell/platform/embedder/embedder.h",
      "new_id": "1d656e355baa38e2d54f80243c21efe877bcce31",
      "new_mode": 33188,
      "new_path": "shell/platform/embedder/embedder.h"
    }
  ]
}