Bcachefs Fixes Pull Once Again Frustrates Linus Torvalds - Two Choices Offered

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • PuckPoltergeist
    replied
    Originally posted by Uiop View Post
    Hopefully, noone will get offended by what Kent wrote, as it is just his personal and professional opinion.
    The kind of opinion which Kent is displaying demonstrates a commitment to correctness, reliability and robustness. That's what I appreciate.
    I don't think he is boosting himself, I think that every other filesystem should also display such high standards of commitment to reliability.
    The problem is that other filesystems (i.e. their devs) don't show such commitment. They don't take the user's data seriously enough. What I appreciate in Kent's mails, and what differentiates him from others, is commitment to important principles.
    In my eyes it's offending to allege this, to say devs don't care about users data. They don't emphasize in every second sentence. It's just obviously that data integrity has the highest priority. And for me it's not professional to imply other devs don't care (like Kent does again and again). And that's about Josef mail.

    Leave a comment:


  • oleid
    replied
    Originally posted by Developer12 View Post

    These build failures are impacting enough people that Torvalds is perfectly willing to rip out the whole filesystem.
    They are nice to each other again. Please simply read the mailing list.

    Leave a comment:


  • Developer12
    replied
    Originally posted by oleid View Post

    I think you mixed something up here. You logically connected "a lot of people" with "big endian". Those two don't go together.

    But as you most certainly read in the following discussion, they are discussing big endian ci. So it will get solved.
    "so it will get solved" when he's finally called out on his bullshit.

    These build failures are impacting enough people that Torvalds is perfectly willing to rip out the whole filesystem.

    Leave a comment:


  • Daktyl198
    replied
    Originally posted by mdedetrich View Post
    In reality this entire thing is a diversion, what should really be discussed is why the flying fuck in 2024 (almost 2025), does Linux not have a nightly CI build against current in progress branch. This has been completely standard for open source projects for decades, and instead in their infinite wisdom Linux kernel dev's thought that offloading this to users wouldn't be problematic. My gosh.
    Because pushing patches on a mailing list for Linus to pull into his own git tree is a fucking AWFUL way of doing software development and does not lend itself to using a CI at all. They'd have to move to a centralized hosted and managed git repo with CI integration (some form of GitHub/GitLab/etc) but all the old hats refuse to change the way they've developed software since the 70s. God forbid they learn any new processes in order to welcome way more developers, instead it's this extremely weird and hard to learn form of pushing patches where you have to do 5 hours of research just to know who to talk to about your 1 line patch instead of just submitting a PR and tagging it with the correct subsystem.

    Leave a comment:


  • Daktyl198
    replied
    Originally posted by mdedetrich View Post

    Learn to read. I said that the only systems with big endian are either decades old OR are mainframes.
    Not in the vast majority of your comments. But pop off lol.

    Originally posted by mdedetrich View Post
    IBM-z system is a mainframe, I don't think its realistic to expect Kent to dump hundreds of thousands, if not millions to buy a mainframe for his home but I could be wrong.​
    Instead of having Kent buy a mainframe, how about he just stop touching code so far outside the reach of his filesystem that he's breaking builds on hardware he doesn't support or ever intend to support... and then submitting those changes the day before RC...

    Originally posted by mdedetrich View Post
    And when Linus wrote this filesystems, these processes didn't even exist something that Kent ironically pointed out to him
    Which has nothing to do with Kent's original taunt.
    Last edited by Daktyl198; 07 October 2024, 09:16 PM.

    Leave a comment:


  • LockedPotato
    replied
    Originally posted by mdedetrich View Post

    He didn't push patches with zero testing, stop spreading lies.
    I mean...

    And before you start whining - again - about how you are fixing bugs, let me remind you about the build failures you had on big-endian machines because your patches had gotten ZERO testing outside your tree.

    I was hoping and expecting that bcachefs being mainlined would actually help development. It has not. You're still basically the only developer, there's no real sign that that will change, and you seem to feel like sending me untested stuff that nobody else has ever seen the day before the next rc release is just fine.

    So if this is just your project and nobody else is expected to participate, and you don't care about the fact that you break the mainline build, why the hell did you want to be in the mainline tree in the first place?
    Literally read the article. Which seven mouth breathers liked your post?

    Leave a comment:


  • Errinwright
    replied
    Originally posted by PuckPoltergeist View Post
    Already read this. Seems my understanding doesn't match yours


    MM-devs NAKed, VFS-devs NAKed, the guy who says, he's the only one who knows right, pushed through his own tree. I'm reading fsdevel...


    It's running for next and stable. But I forgot, bcachefs is so mature and stable and perfect, it doesn't need any stable-fixes.

    As I said, we had this several times before. It's just another round with other player(s). Taking my popcorn and enjoy the show
    Should perhaps re-read if that is your conclusion

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by PuckPoltergeist View Post
    edit2: Kent is "crucified" for offending others and not working together, ignoring change request over and over again.
    For the crucified-part:

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by Uiop View Post
    So, we should kick Kent out of the Linux mainline because IBM isn't interested in his filesystem, and because IBM doesn't care about the rest of us, the peasants.

    Excellent argument... it proves what I have been afraid of.
    That's what you said. Don't know, where you read this from?

    Leave a comment:


  • PuckPoltergeist
    replied
    Originally posted by Uiop View Post

    Also, I'm obviously not talking about IBM donating hardware to Kent.

    I'm talking about IBM not donating their z-architecture for the Linux kernel test builds.
    And I'm just addressing the part with the interests. Corporations spending money in things they are interested in. IBM is interested in Linux, obviously. If they are interested in bcachefs too, they would spent hardware for this. But they aren't, they are just interested in a very small niche. Most Linux users a irrelevant as fuck to them.

    edit: Oh and btw. I would expect IBM is more interested in XFS today, as they own Red Hat now.

    edit2: Kent is "crucified" for offending others and not working together, ignoring change request over and over again.
    Last edited by PuckPoltergeist; 07 October 2024, 03:56 PM.

    Leave a comment:

Working...
X