All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Why no linux-2.6.8.2? (was Re: new dev model)
Date: Thu, 7 Oct 2004 01:31:39 -0400	[thread overview]
Message-ID: <200410070134_MC3-1-8BA9-A215@compuserve.com> (raw)

Why has linux 2.6.8 been abandoned at version 2.6.8.1?

There exist fixes that could go into 2.6.8.2:

        process start time doesn't match system time
        FDDI frame doesn't allow 802.3 hwtype
        NFS server using XFS filesystem on SMP machine oopses

I'm sure there are more...

So why is 2.6.8.1 a "dead branch?"


--Chuck Ebbert



             reply	other threads:[~2004-10-07  5:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07  5:31 Chuck Ebbert [this message]
2004-10-07  4:46 ` Why no linux-2.6.8.2? (was Re: new dev model) alan
2004-10-07  5:49   ` Jeff Garzik
2004-10-07  5:39 ` Trent Lloyd
2004-10-07  5:43 ` Jeff Garzik
2004-10-10 16:41 ` Tomasz Torcz
  -- strict thread matches above, loose matches on Subject: below --
2004-10-07  7:05 Chuck Ebbert
2004-10-07  7:52 ` Trent Lloyd
2004-10-07  7:05 Chuck Ebbert
2004-10-07  7:15 ` Jeff Garzik
2004-10-07 13:55 ` Alan Cox
2004-10-07 14:21 Chuck Ebbert
2004-10-07 16:37 Chuck Ebbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200410070134_MC3-1-8BA9-A215@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.