public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	Nick Warne <nick@linicks.net>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	linux-kernel@vger.kernel.org, webmaster@kernel.org
Subject: Re: 2.6.14.5 to 2.6.15 patch
Date: Wed, 4 Jan 2006 15:41:06 -0800	[thread overview]
Message-ID: <20060104234106.GB15724@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0601041530000.19134@shark.he.net>

On Wed, Jan 04, 2006 at 03:31:01PM -0800, Randy.Dunlap wrote:
> On Wed, 4 Jan 2006, Alistair John Strachan wrote:
> 
> > On Wednesday 04 January 2006 23:13, Greg KH wrote:
> > > On Wed, Jan 04, 2006 at 10:58:24PM +0000, Alistair John Strachan wrote:
> > > > On Wednesday 04 January 2006 22:31, Greg KH wrote:
> > > > [snip]
> > > >
> > > > > > > The issue I hit was we have a 'latest stable kernel release
> > > > > > > 2.6.14.5' and under it a 'the latest stable kernel' (or words to
> > > > > > > that effect) on kernel.org.
> > > > > > >
> > > > > > > Then when 2.6.15 came out, that was it!  No patch for the 'latest
> > > > > > > stable kernel release 2.6.14.5'.  It was GONE!
> > > > > >
> > > > > > Yes, I brought this up a couple of weeks ago, but I was told
> > > > > > that I was wrong (in some such words).
> > > > > > I agree that it needs to be fixed.
> > > > >
> > > > > How would you suggest that it be fixed?
> > > >
> > > > It's difficult, but perhaps providing a link to the latest "stable team"
> > > > release in addition to Linus's release would solve the problem.
> > >
> > > But what happens when we release a 2.6.14.y release and a 2.6.15.y
> > > release at the same time (as people have requested this in previous
> > > threads...)?  What would show up where?
> >
> > You're right, it's complicated. In that case I'd still opt for showing
> > 2.6.15.y, as the vast majority of people manually installing vanilla kernels
> > will either be on the latest-ish kernel, or have a clue about what they're
> > doing (who doesn't know the ftp URL off by heart now).
> 
> I agree.  I think that one previous -stable patch version should always
> be listed there, even if we think that 2.6.N is stable.  :)

I don't at all.  If we do that, people will assume that they need to
wait till 2.6.N.1 before trying that kernel (as it wouldn't be "stable"
otherwise.)  So no one will test it, to really generate the bug reports
that we need to get to that .1 release.

Or should we just throw out a .1 release with the first simple patch
that comes along just to make the kernel.org page update properly?  I
don't think so...

thanks,

greg k-h

  reply	other threads:[~2006-01-04 23:41 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 17:10 2.6.14.5 to 2.6.15 patch Nick Warne
2006-01-04 17:18 ` Jesper Juhl
2006-01-04 17:28   ` Nick Warne
2006-01-04 17:36     ` Randy.Dunlap
2006-01-04 17:39       ` Nick Warne
2006-01-04 18:34         ` Alistair John Strachan
2006-01-04 19:53           ` Nick Warne
2006-01-04 20:10             ` Matan Peled
2006-01-04 20:10             ` Alistair John Strachan
2006-01-04 22:01               ` Greg KH
2006-01-04 22:10                 ` Nick Warne
2006-01-04 22:15                   ` Greg KH
2006-01-04 22:20                     ` Nick Warne
2006-01-04 22:30                       ` Greg KH
2006-01-04 22:30                       ` Jesper Juhl
2006-01-04 22:36                         ` Nick Warne
2006-01-04 23:10                           ` Greg KH
2006-01-04 22:49                       ` Grant Coady
2006-01-04 22:16                   ` Randy.Dunlap
2006-01-04 22:31                     ` Greg KH
2006-01-04 22:58                       ` Alistair John Strachan
2006-01-04 23:13                         ` Greg KH
2006-01-04 23:28                           ` Alistair John Strachan
2006-01-04 23:31                             ` Randy.Dunlap
2006-01-04 23:41                               ` Greg KH [this message]
2006-01-04 23:42                                 ` Randy.Dunlap
2006-01-04 23:49                                 ` Jesper Juhl
2006-01-05  7:30                                 ` Jan Engelhardt
2006-01-04 22:49                 ` Alistair John Strachan
2006-01-04 23:12                   ` Greg KH
2006-01-04 23:26                     ` Alistair John Strachan
2006-01-05  0:08                   ` H. Peter Anvin
2006-01-05 15:25                     ` Alistair John Strachan
2006-01-05 15:37                       ` Jesper Juhl
2006-01-05 15:55                         ` Alistair John Strachan
2006-01-05 16:42                           ` H. Peter Anvin
2006-01-04 22:01           ` Greg KH
2006-01-04 22:50             ` Alistair John Strachan
2006-01-04 17:40     ` Jesper Juhl
2006-01-04 17:45       ` Nick Warne
2006-01-04 17:50         ` Jesper Juhl
2006-01-04 17:51           ` Randy.Dunlap
2006-01-04 17:56             ` Jesper Juhl
2006-01-04 18:08               ` Mark Lord
2006-01-04 18:13                 ` Jesper Juhl
2006-01-04 21:13                   ` Grant Coady
2006-01-04 21:20                     ` Jesper Juhl
2006-01-04 17:56             ` Nick Warne
2006-01-04 18:27               ` Steven Rostedt
2006-01-04 21:17                 ` Jesper Juhl
2006-01-04 21:48                   ` Steven Rostedt
2006-01-04 22:20                     ` Steven Rostedt
2006-01-04 17:19 ` Marc Haber
2006-01-04 17:29   ` Steven Rostedt
2006-01-04 17:29 ` YOSHIFUJI Hideaki / 吉藤英明
2006-01-04 18:15 ` Matthias Andree
  -- strict thread matches above, loose matches on Subject: below --
2006-01-05 17:14 mreuther

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=20060104234106.GB15724@kroah.com \
    --to=greg@kroah.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    --cc=rdunlap@xenotime.net \
    --cc=s0348365@sms.ed.ac.uk \
    --cc=webmaster@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox