Re: The naming wars continue...

From: William Lee Irwin III (wli_at_holomorphy.com)
Date: 10/23/04

  • Next message: Jack O'Quin: "Re: [PATCH] Realtime LSM"
    Date:	Fri, 22 Oct 2004 17:04:01 -0700
    To: Linus Torvalds <torvalds@osdl.org>
    
    

    On Fri, Oct 22, 2004 at 03:05:13PM -0700, Linus Torvalds wrote:
    > Linux-2.6.10-rc1 is out there for your pleasure.
    > I thought long and hard about the name of this release (*), since one of
    > the main complaints about 2.6.9 was the apparently release naming scheme.
    > Should it be "-rc1"? Or "-pre1" to show it's not really considered release
    > quality yet? Or should I make like a rocket scientist, and count _down_
    > instead of up? Should I make names based on which day of the week the
    > release happened? Questions, questions..
    > And the fact is, I can't see the point. I'll just call it all "-rcX",
    > because I (very obviously) have no clue where the cut-over-point from
    > "pre" to "rc" is, or (even more painfully obviously) where it will become
    > the final next release.
    > So to not overtax my poor brain, I'll just call them all -rc releases, and
    > hope that developers see them as a sign that there's been stuff merged,
    > and we should start calming down and seeing to the merged patches being
    > stable soon enough..

    AFAICT the point is being able to refer to it by name and the only
    relevant property of the name is that it's distinct from all others.
    This does as well as most any other scheme giving each unique names.
    I'd be fine with nightly point releases, though I don't insist.

    On Fri, Oct 22, 2004 at 03:05:13PM -0700, Linus Torvalds wrote:
    > So without any further ado, here's 2.6.10-rc1 in testing. A fair number of
    > patches that were waiting for 2.6.9 to be out are in here, ranging all
    > over the map: merges from -mm, network (and net driver) updates, SATA
    > stuff, bluetooth, SCSI, device models, janitorial, you name it.
    > Oh, and the _real_ name did actually change. It's not Zonked Quokka any
    > more, that's so yesterday. Today we're Woozy Numbat! Get your order in!
    > Linus
    > (*) In other words, I had a beer and watched TV. Mmm... Donuts.

    Sounds like a good way to come up with a new name to me. Cheers!

    -- wli
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Jack O'Quin: "Re: [PATCH] Realtime LSM"

    Relevant Pages

    • Re: The naming wars continue...
      ... On Fri, 22 Oct 2004, Linus Torvalds wrote: ... > the main complaints about 2.6.9 was the apparently release naming scheme. ... > and we should start calming down and seeing to the merged patches being ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: The naming wars continue...
      ... >>the main complaints about 2.6.9 was the apparently release naming scheme. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices
      ... you're comparing non-unix to unix operating systems and you're ... So, lets say for windows, you believe that when having two identical USB CDRs ... the user will prefer the letter naming scheme. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: gigabit trouble
      ... > is or possibly isn't in that annoying new naming scheme? ... > Anyhow, on transmit from the celeron box, under extreme benchy ... > This may be due to fiddling with said wmem, etc values, I set some of them ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: cdrecord hangs my computer
      ... > hda..hdx in an order depending on the loading order of the device ... you can have all programs use their own random naming scheme and use ... .cdrecordrc and edit that instead, but then you have to remember to edit ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)