Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Operating Systems Upgrades Linux

Linux 3.10 Merge Windows Closes 74

hypnosec writes "Linus Torvalds has released the Linux 3.10-rc1 kernel marking the closure of the 3.10 merge window. The Linux 3.10-rc1 is the second biggest rc release in years and the closure of the merge windows means that the features expected out of the Linux 3.9 successor are chalked out. "So this is the biggest -rc1 in the last several years (perhaps ever) at least as far as counting commits go," Linus notes in the release announcement."
This discussion has been archived. No new comments can be posted.

Linux 3.10 Merge Windows Closes

Comments Filter:
  • by boshvark ( 2599623 ) on Monday May 13, 2013 @12:18PM (#43711111) Homepage
    So Linux is finally merging with Windows... uh, that can't be right. I guess windows will now merge when you close them? No, that doesn't make sense either, so maybe it's a new Unity feature.
    • Or maybe they're bringing Wine into the kernel? No, that's NDISwrapper.
    • by Samantha Wright ( 1324923 ) on Monday May 13, 2013 @12:22PM (#43711157) Homepage Journal
      No, no, it says quite clearly that they're only merging with Windows 3.1, which is barely Windows by any useful definition. Didn't you RTFA? Jeez, the nerve of some people...
    • by i kan reed ( 749298 ) on Monday May 13, 2013 @12:24PM (#43711167) Homepage Journal

      This is a phenomenon known as a Garden path sentence []. The phrasing leads you to believe that windows is a singular noun, when it is in fact a plural noun with a different meaning. For anyone still confused: these are the windows to merge changes into source-control before release.

      • by Anonymous Coward on Monday May 13, 2013 @12:50PM (#43711485)

        No, the problem here isn't a garden path sentence, the problem is illiterate Slashdot editorial processes as usual. The right headline was "Linux 3.10 merge window closes" but the usual brain damage morphed that into what you see now.

        If there were several "merge windows" then that would be plural, but the verb changes to agree, that's how English works. So you'd get "Linux 3.10 merge windows close".

        You can write the sentence "Linux 3.10 merge windows closes" in English, but you need "window" to be a verb and then the "merge windows" noun + verb assembly becomes a singular compound noun which you can use with the verb "closes". You would probably never want to do this, and it's not what anybody at Slashdot intended, but it's a possible English sentence. Shakespeare used to treat "window" as a verb, so you wouldn't necessarily be in the worst company, but Shakespeare was a fucking genius, the people editing Slashdot can't even compete with those monkeys Mr Burns had working on A Tale of Two Cities.

      • This is a phenomenon known as a Garden path sentence [].

        I'm pretty sure it's just a crappily written one.

  • You got an extra s in there, yo.

    "Linux 3.10 Merge Windows" had me getting ready to scout out a new OS.

    The merge window closing, however, is a good thing.

  • by Anonymous Coward on Monday May 13, 2013 @12:38PM (#43711323)

    They changed the kernel enough so that the NVIDIA binary blobs are börken (sic) again! Something about whether is a real 2.4 kernel and whatnot. It seems just to be a test, but its anal and börken! I understand that NVIDIA is a commercial company and as such cannot keep up to the rate of development of OSS developers.

    • Re: (Score:2, Informative)

      by Anonymous Coward

      Same goes for ATI's fglrx, which was broken due to removal of some deprecated procfs functions. This was the first time I got a lemon by updating kernel during merge window.

    • by Anonymous Coward

      Get some sound advice []

    • yep/me-too/%#$!! the best annoying dumb trick comes via dkms (Dynamic Kernel Module Support). so there's was a working graphics module (for nvidia blob 304.88) then unlucky fool (which would be me) does an update/dist-upgrade, and so dkms uninstalls the working module, attempts to install a new module, which fails to compile ("nv-i2c.c function ‘nv_i2c_del_adapter’ : error: void value not ignored as it ought to be") and now we're left with a box which will have no graphics upon reboot.


    • by Anonymous Coward

      I've personally found that if you get your kernel module into the baseline, the kernel devs will generally update it when the kernel interfaces change, assuming that the module itself hasn't become totally obsolescent; I wonder if nVidia has considered this?

    • So I guess you'll not buy Nvidia again? Because they obviously don't care about your Linux experience. Because if they did, they'd open source their driver, and work to get it accepted into the Linux mainline tree. So that then the kernel developers would maintain it for them. For free.

      Oohh ohh.

      Nvidia had a charming air
      All cheap and debonair
      You found so sweet
      And so you took Nvidia in
      Your sheets still warm with him
      Now filled with filth and foul disease
      As time wore on Nvidia proved
      A debt-ridden drunken mess

      • by dbIII ( 701233 )
        I don't think the current bunch at Nvidia would open their drivers until the day after software patents are abolished. There's some ex-SGI people there that got burnt by a 3D graphics software patent troll.
        So don't rant at Nvidia, rant at the stupid IP system that has made them too paranoid to release anything that a patent troll can use against them. Keep in mind that it's the sort of environment where John Carmack eventually had to pay off a troll to continue to use the algorithm that had been named aft
  • list of changes (Score:4, Informative)

    by ssam ( 2723487 ) on Monday May 13, 2013 @12:47PM (#43711437)

    For folk who even after RTFA wonder whats new in 3.10, the best source is probably LWN [] []

  • Only a day [] after the last installment! Though this article only has 3 possible candidates, to that article's 4... those candidates are 3/5s of all the words in the headline, to that other article's 4/7.

  • by Gothmolly ( 148874 ) on Monday May 13, 2013 @02:09PM (#43712521)

    Are the things I care about - and I suspect most people do too, even if they don't know about it. The eed to transparently (or not!) accelerate spinning drives with SSD is a killer feature. I'm currently running a homebrew NAS on Linux and my VMWare hosts insist on doing sync mounts - effectively killing performance. By shimming some SSD in front of that, my IO latency bottleneck essentially goes away. (Lets leave ZFS out of this). "Desktop" distros will love this too - I see a simple "wizard" that asks "I see you have an SSD installed - would you like to accelerate access to your HD? Click yes and specify a maximum cache size" Presto - an instant increase in performing most tasks.

    • "Desktop" distros will love this too - I see a simple "wizard" that asks "I see you have an SSD installed - would you like to accelerate access to your HD? Click yes and specify a maximum cache size"

      Might not happen. Currently any distro does not even turn on discard for a SSD automatically (due to TRIM implementation being a bit broken in Linux []).

      • That's a separate problem. The basics of using fast storage to cache slow storage are what's critical here - whether you have dodge block device support is irrelevant. A few different options are marked for inclusion in 3.9 as experimental, and slated for 3.10.

  • Am I the only one who thinks having a version number which is subject to getting rounded off is a terrible terrible idea?

    "Oops looks like this release has a trailing 0 on there... *delete*."

    • by Anonymous Coward

      Apparently yes, you are the only one.

    • Re:3.1 vs 3.10!? (Score:4, Informative)

      by jones_supa ( 887896 ) on Monday May 13, 2013 @02:43PM (#43712893)

      Am I the only one who thinks having a version number which is subject to getting rounded off is a terrible terrible idea?

      "Oops looks like this release has a trailing 0 on there... *delete*."

      Terrible idea? That's how version numbers work. They are not ordinary decimal numbers, so you cannot round them like that.

    • by Anonymous Coward

      Version numbers are not floating point numbers. They are a set of integers separated by punctuation. If you treat them like anything else, you're doing it wrong.

      Try your drainbead logic on IP addresses so we can continue laughing at you.

    • by Xtifr ( 1323 )

      You're probably not the only one, but that doesn't mean that the set of people who think it's a terrible idea are any less misguided or wrong. This is normal and standard and most tools for tracking versions assume version numbers work this way. Including the tools that do dynamic linking at run-time for you. In fact, for libraries, it's mandatory to do this if you have more than ten backwards-compatible releases in a series. A change in the second number of a library's version indicates that it's backwards

    • by sdnoob ( 917382 )

      okay.. how about apple's way:

      version 3.x

      there. much better.

    • Do we really have to have this conversation every single time any software releases version_dot_ten? It's getting a bit old at this point.

  • Linux is merging with Windows?

UFOs are for real: the Air Force doesn't exist.