)]}'
{
  "commit": "4e040eb22e5fa543b9c0fc910f1350ae6fe6f448",
  "tree": "cefb846254b193d0d725be14a40d313d455e17f2",
  "parents": [
    "a601c1e794fff180ca5e9a2005f98a5f4155d0ef",
    "cd734869c71512e332a4370abb1581e060d5d209"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Fri Aug 28 10:15:54 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Aug 28 10:15:54 2026 +0200"
  },
  "message": "Rollup merge of #161889 - maxdexh:ptr-read-ownership, r\u003dChrisDenton\n\nAdd link to ownership section in ptr::read docs\n\nThis one has annoyed me for a while but I never found it worth fixing.\n\nOne of the safety requirements of `read` is that you handle ownership correctly.\n\nAll `read`-like functions in the `ptr` module (e.g. `copy`, `read_unaligned`) state that \"just like `read`\", you have to take care around this, and they link to the section on ownership in the `read` docs.\nHowever, `read` does not do so in its own safety requirements, and worse yet, you have to *scroll down* to see the section.\n\nEvery so often I look at this function and think ownership is missing from the docs, before remembering this.\nThis PR just adds a link to make sure users don\u0027t miss this.\n\nr? libs\n",
  "tree_diff": []
}