)]}'
{
  "commit": "c3af6292ecbb2458fee6fa9f62a4d50faadda579",
  "tree": "09babc00255cf7d09317b79e40abd10f60899fac",
  "parents": [
    "0df64c57843a9612c68dd78bafa133f5b5d340c4",
    "d589d2f40b78fab69bc706c821bd459244d9d1d5"
  ],
  "author": {
    "name": "Matthias Krüger",
    "email": "476013+matthiaskrgr@users.noreply.github.com",
    "time": "Mon Nov 17 21:47:58 2025 +0100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Mon Nov 17 21:47:58 2025 +0100"
  },
  "message": "Rollup merge of #147077 - joboet:mov_kernel_copy_sys, r\u003dibraheemdev\n\nstd: move `kernel_copy` to `sys`\n\nPart of rust-lang/rust#117276.\n\nThe current organisation of the `kernel_copy` mechanism used to specialise `io::copy` on Linux necessitated circular links between the `io::copy` module and the implementation in `sys::pal::unix::kernel_copy`, as well as presenting an exception to the tidy PAL rule that forbids OS-based `#[cfg]`s outside of `sys` and `os`.\n\nThis PR fixes this by moving `kernel_copy` to `sys` (as per rust-lang/rust#117276) and returning a `CopyState` from that function specifying whether `io::copy` should use its fallback. The `kernel_copy` function on other platforms just unconditionally returns `CopyState::Fallback`.\n",
  "tree_diff": []
}