Slashdot Mirror


Linux 3.10 Merge Windows Closes

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."

18 of 74 comments (clear)

  1. Merge Windows Closes by boshvark · · Score: 5, Funny

    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.

    --
    There's always money in the banana stand.
    1. Re:Merge Windows Closes by Samantha+Wright · · Score: 5, Funny

      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...

      --
      Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
    2. Re:Merge Windows Closes by i+kan+reed · · Score: 4, Informative

      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.

    3. Re:Merge Windows Closes by Anonymous Coward · · Score: 4, Informative

      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.

  2. WTF at the title by kernelpanicked · · Score: 2

    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.

    --
    Ubuntu: If at first you don't succeed, blindly slap a sudo in front of it
  3. NVIDIA borken again... by Anonymous Coward · · Score: 3, Informative

    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.

    1. Re:NVIDIA borken again... by Anonymous Coward · · Score: 2, Informative

      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.

  4. list of changes by ssam · · Score: 3, Informative

    For folk who even after RTFA wonder whats new in 3.10, the best source is probably LWN
    https://lwn.net/Articles/548834/
    https://lwn.net/Articles/549477/

    1. Re:list of changes by greg1104 · · Score: 2

      You can't have a single stream of bug numbers in a true multi-vendor open source project. RedHat can assign something a bug number, but so can the Debian team, Canonical, etc. Seeing a unique bug number for a free software project is actually a bad sign. It usually means a single person or company is behind that project. What you want instead is a developer community that can survive losing any one member.

    2. Re:list of changes by DragonWriter · · Score: 2

      You can't have a single stream of bug numbers in a true multi-vendor open source project.

      Since there are schemes for assignment of unique identifiers that allow multiple parties to generate their own identifiers without coordination except on a standard scheme, and to do so maintaining uniqueness, this isn't true.

    3. Re:list of changes by greg1104 · · Score: 2

      Of course you can add a prefix to each vendor and therefore allow them to share a larger bug address space. The simplest scheme is to make RedHat bugs RH-xxxxxx, Debian ones DE-xxxxxx, etc. The shared allocation approach taken by CVE numbering could be used too. I would call that a combined or aggregated stream of bug numbers rather than a single stream; that's a hair splitting distinction though.

      Regardless, to be effective for tracking regular bugs and features, you would also need resources to coordinate things like tagging duplicates across vendors. A Linux bug might be upstream of ten different distribution bugs. When it's fixed in the kernel, which bug number should the commit refer to?

      With a complicated enough mapping of vendor bug number to kernel bug number, you could try to capture this information too. That's another shared resource someone needs to maintain though. It's overhead with little perceived value to the individual vendors involved. Linux distributors are motivated to get bug fixes pushed upstream. There's a benefit in it for them. There's little benefit for any one vendor to having a universal bug number mapping tracker, relative to the complexity you'd need to maintain a useful one. Even if you had most of the major distributions agreeing on the shared numbering scheme, there's also time needed to coordinate the bug ids for contributions to the project outside of those vendors.

      The number of CVE incidents is low enough (and the issues serious enough) that the bug id mapping they do is not a serious drag on development. One of the reasons the Linux kernel can innovate at a high rate is because it's not burdened by this sort of management issue most of the time.

  5. Re:Yes, nice. But why is this a story? by serviscope_minor · · Score: 5, Insightful

    Everybody concerned will already have this news from other sources.

    You are mistaken.

    I care enough to RTFA, and I got the story here.

    Why? I care about kernel development because it interests me, but I don't care about it enough to require absoloutely up to the minute coverage. So, slashdot is an excellent place to get it, and there are often useful comments to boot.

    Basically, you could say the same about any story: anyone who cares enough could get the news faster from a domain specific source.

    Everybody else does likely not care, also because typical users use distro-kernels and not self-compiled kernels from kernel.org.

    Huh? These features will make it into distros soonish, and secondly since when is slashdot only the domain of typical users.

    And this is not even the kernel release, but the closing of the merge-window,

    The two are equivalent from this perspective: the actual release will have no new features.

    --
    SJW n. One who posts facts.
  6. Re:Yes, nice. But why is this a story? by swillden · · Score: 2

    Everybody concerned will already have this news from other sources.

    I'm interested, and I learned of it here.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  7. I'm with you on this. by Robert+Frazier · · Score: 2

    I'm happy to see the story. I regularly look at 4 or 5 websites, only 2 of which have anything to do with computing technology, and this is one of them, which I've been following for quite a while. So, although it may not be ideal, I still get most of my technology updates on slashdot. (Other than ones in which I'm professionally interested, the site I spend most time on also deals with technology, but of a different sort: mechanical watches.)

    Best wishes,
    Bob

  8. mainline flashcache and bcache by Gothmolly · · Score: 4, Informative

    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.

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:mainline flashcache and bcache by jones_supa · · Score: 2

      "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).

  9. Re:3.1 vs 3.10!? by jones_supa · · Score: 3, Informative

    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.

  10. Re:3.1 vs 3.10!? by jones_supa · · Score: 2

    int major = round(3);
    int minor = round(10);
    printf("%d.%d", major, minor);