• LeFantome@programming.dev
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    23 hours ago

    That is a personality issue, not a code emergency.

    There were two dozen patches submitted for 6.17 that were never merged. What has the fall-out been? Where are all the stories about data loss? I am sure they would hit the front page.

    The file system can improve but it is already fine.

    • gian @lemmy.grys.it
      link
      fedilink
      English
      arrow-up
      3
      ·
      14 hours ago

      That is a personality issue, not a code emergency.

      True, but it is an indication that the developer cannot follow a common rules. Simply Torvalds was tired of how he behaved.

      There were two dozen patches submitted for 6.17 that were never merged. What has the fall-out been? Where are all the stories about data loss? I am sure they would hit the front page.

      And so ? A patch can be submitted but never merged, for whatever reason. Problem is: these two dozen patches were submitted during the -RC cycle ?

      The file system can improve but it is already fine.

      Good. Now it it the developer that need to improve his attitude to work in teams.

    • whaleross@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      22 hours ago

      The fallout for people knowingly risking their data beta testing a filesystem that is still in experimental and some users running into issues and possibly corruption?

      There are no stories because it is not a story when a test environment for finding bugs fails and the bugs get fixed. Nobody with data they can not lose are putting it on bcachefs because why would they.

      Thanks for running a test environment though. Please take backups of anything important, just in case.