)]}'
{
  "commit": "c39b1dc86b0af53d0aee5ca0f1a32ab79408167d",
  "tree": "dfa95096d6c305f4a3f380ab32dffa5e62f56397",
  "parents": [
    "5c82e0dc025c8df3328af3cffd64b830b3bdb2b4"
  ],
  "author": {
    "name": "Jan Schär",
    "email": "jan@monogon.tech",
    "time": "Mon Aug 26 17:21:14 2024 +0200"
  },
  "committer": {
    "name": "Jan Schär",
    "email": "jan@monogon.tech",
    "time": "Tue Sep 10 14:50:21 2024 +0000"
  },
  "message": "osbase/gpt: sync device after writing each GPT\n\nThis makes it safer to update the GPT. Without the first sync call, it \ncould for example happen that both GPTs are partially written to disk \nwhen the system loses power, resulting in both GPTs being corrupted. The \nsecond sync call ensures that the GPT update is committed to disk and \nwill not be rolled back, and also that both GPTs are valid after the \ncall to Write returns.\n\nChange-Id: I50b3cabee4ee8a3162766812e945e129358dd875\nReviewed-on: https://review.monogon.dev/c/monogon/+/3360\nReviewed-by: Lorenz Brun \u003clorenz@monogon.tech\u003e\nTested-by: Jenkins CI\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "033a34d1bbb2646f6e656d201e4ea362c3960fce",
      "old_mode": 33188,
      "old_path": "osbase/gpt/gpt.go",
      "new_id": "1c6681646e82f36656c081ce2bc6260806ca7601",
      "new_mode": 33188,
      "new_path": "osbase/gpt/gpt.go"
    }
  ]
}