LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Chuck Ebbert <cebbert@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: 2.6.18-stable release plans?
Date: Tue, 23 Jan 2007 23:50:45 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701232332540.20138@iabervon.org> (raw)
In-Reply-To: <9a8748490701221623q1b61f03fva7b0ad7e7f30316f@mail.gmail.com>

On Tue, 23 Jan 2007, Jesper Juhl wrote:

> Now that 2.6.19 is out, most likely not.  -stable releases are made
> for the latest stable 2.6.x kernel, once 2.6.x+1 is out that's the one
> -stable patches are made for (2.6.16 is an exception)..

There's generally a bit of overlap. 2.6.17.14 was about the same time as 
2.6.18.1, and 2.6.18.6 was after 2.6.19.1. But 2.6.18.x must be over now, 
because the -stable team didn't release a 2.6.18.7 to match 2.6.19.2, and 
all of 2.6.x except for 2.6.19.2 has that weird file corruption bug 
(although rarely triggered).

	-Daniel
*This .sig left intentionally blank*

  parent reply	other threads:[~2007-01-24  4:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-22 22:13 Chuck Ebbert
2007-01-23  0:23 ` Jesper Juhl
2007-01-23 13:38   ` [Proposal] " Sunil Naidu
2007-01-23 17:41     ` Stefan Richter
2007-01-23 19:25       ` Sunil Naidu
2007-01-23 20:06         ` Stefan Richter
2007-01-23 20:33   ` Chuck Ebbert
2007-01-23 20:56     ` Adrian Bunk
2007-01-24  4:50   ` Daniel Barkalow [this message]
2007-01-24 13:30 Chris Rankin
2007-01-24 14:37 ` Hugh Dickins
2007-01-24 15:06 Chris Rankin
2007-01-24 15:40 ` Hugh Dickins
2007-01-24 15:53 Chris Rankin
2007-01-24 16:12 ` Hugh Dickins
2007-01-24 17:33   ` Chris Rankin
2007-01-24 16:28 ` Mark Rustad
2007-01-24 22:37   ` Chris Rankin
2007-01-24 23:11     ` Alan
2007-01-24 23:05       ` Chris Rankin
2007-01-24 23:32       ` Mark Rustad
2007-01-24 23:45         ` Chris Rankin
2007-01-25  1:00           ` Ken Moffat
2007-01-25  9:16             ` Chris Rankin
2007-01-25 19:36               ` Ken Moffat
2007-01-26 13:02                 ` Chris Rankin
2007-01-25 23:26               ` Alistair John Strachan
2007-01-25  3:05           ` Mark Rustad
2007-01-25 21:04       ` Matt Mackall
2007-02-02  4:02     ` Valdis.Kletnieks
2007-02-02  6:47       ` Jon Masters
2007-02-02  8:17         ` Valdis.Kletnieks
     [not found] <BC3E207A-1A56-4032-9619-910E80281E9C@gmail.com>
2007-01-25  8:51 ` Chris Rankin

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=Pine.LNX.4.64.0701232332540.20138@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=cebbert@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.18-stable release plans?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).