V2 Of KDBUS Published For Linux Kernel Review

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • Apopas
    Senior Member
    • Mar 2009
    • 1292

    #11
    Never say never!

    Comment

    • nilssab
      Junior Member
      • Jan 2014
      • 34

      #12
      Originally posted by mark45 View Post
      Linus Torvalds said a major version bump occurs when the minor version gets up to like 40. No major version bump based on features, google for more info from Torvalds.
      Well, I have heard him say this at many events. But that doesn't mean that we cannot and shouldn't try to revise our opinion on that idea by discussing it.
      Personally I find this too seem like such a feature that would warrant a new major version, and that doing a major version bump when it gets accepted or when that code is considered stable would make sense for many users.
      but I feel I have likely missed something that would equally warrant a similar bump, so I ask what the community thinks of this. Would it demerit other large chances and are there other reasons to not do this? (save for the opinion of Linus)

      Comment

      • Stellarwind
        Phoronix Member
        • Sep 2011
        • 102

        #13
        Originally posted by nilssab View Post
        Well, I have heard him say this at many events. But that doesn't mean that we cannot and shouldn't try to revise our opinion on that idea by discussing it.
        Personally I find this too seem like such a feature that would warrant a new major version, and that doing a major version bump when it gets accepted or when that code is considered stable would make sense for many users.
        but I feel I have likely missed something that would equally warrant a similar bump, so I ask what the community thinks of this. Would it demerit other large chances and are there other reasons to not do this? (save for the opinion of Linus)
        Transition from 2.4 to 2.6 was a huge step with alot of kernel subsystems changing, but since then development model changed, 2.6 to 3.0 was mostly meaningless, just because version numbers hit high values. kdbus is not important at all, it is a thing you can turn off and loose nothing and in no way major feature for a kernel.

        p.s. always entertaining: http://gentooexperimental.org/~patri...3T09_26_01.txt

        Comment

        • dnebdal
          Senior Member
          • Oct 2010
          • 129

          #14
          Originally posted by Stellarwind View Post
          Transition from 2.4 to 2.6 was a huge step with alot of kernel subsystems changing, but since then development model changed, 2.6 to 3.0 was mostly meaningless, just because version numbers hit high values. kdbus is not important at all, it is a thing you can turn off and loose nothing and in no way major feature for a kernel.

          p.s. always entertaining: http://gentooexperimental.org/~patri...3T09_26_01.txt
          I don't know about "not important at all". If it gets wide enough adoption, it could turn out to be like /proc - perhaps not something you think about every day, but one more useful tool (that some other neat tools depend on).

          Comment

          • curaga
            Senior Member
            • Feb 2008
            • 5924

            #15
            Originally posted by Stellarwind View Post
            Transition from 2.4 to 2.6 was a huge step with alot of kernel subsystems changing, but since then development model changed, 2.6 to 3.0 was mostly meaningless, just because version numbers hit high values. kdbus is not important at all, it is a thing you can turn off and loose nothing and in no way major feature for a kernel.

            p.s. always entertaining: http://gentooexperimental.org/~patri...3T09_26_01.txt
            That's hilarious. Sure I knew dbus was a clusterfuck, but not that it was that bad.

            Comment

            • Stellarwind
              Phoronix Member
              • Sep 2011
              • 102

              #16
              Originally posted by dnebdal View Post
              I don't know about "not important at all". If it gets wide enough adoption, it could turn out to be like /proc - perhaps not something you think about every day, but one more useful tool (that some other neat tools depend on).
              My point was that from kernel pov it is just another IPC mechanism.
              Linus doesn't bump kernel version number every time new filesystem is accepted into mainline, why should this happen for kdbus?

              Comment

              Working...
              X