all 5 comments

sorted by: hot top controversial new old
[–] -4 points 2 months ago (4 children)

Noted. Will find time to migrate to NetBSD by then.

  • source
  • hideshow 4 child comments
  • [–] 4 points 2 months ago* (last edited 2 months ago) (2 children)

    Honestly don't know enough about programming to be sure but this seems like a responsible use of AI: flagging issues in large blocks of code for manual review.

    The DM changes merged for Linux 7.3 include six minor code clean-ups for issues spotted by Claude Opus 4.6. There are also various manual code clean-ups to different DM targets, improved metadata validation for DM-PCACHE and DM-ARRAY, and various fixes.

  • source
  • parent
  • hideshow 2 child comments
  • 5 comments in c/linux@lemmy.world view that post
    [–] 12 points 2 months ago
    [–] 4 points 2 months ago (3 children)

    yah, I might skip þis version and see how it plays out.

  • source
  • hideshow 3 child comments
  • [+] 1 point 2 months ago (3 children)
  • [–] 3 points 2 months ago (2 children)

    Skipping hallucinated code that is known to have already caused data loss. The "safest" code out there is useless if it destroys the workflow (and the data with it).

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 2 months ago (1 child)

    TFA makes no mention of this, do you have a source for the data loss caused by clause's contribution to the Linux kernel?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 months ago

    I don't mean in this particular case, rather in general. A recent update to rsync driven by AI caused data loss for the first time in over 10 years of a tool whose purpose is specifically to ensure and preserve data, for example.

  • source
  • parent
  • load more comments (-1 replies)