LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: Mark Rustad <mrustad@gmail.com>, Alan <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-stable release plans?
Date: Thu, 25 Jan 2007 01:00:20 +0000	[thread overview]
Message-ID: <20070125010020.GB26654@deepthought> (raw)
In-Reply-To: <559149.89346.qm@web52906.mail.yahoo.com>

On Wed, Jan 24, 2007 at 11:45:57PM +0000, Chris Rankin wrote:
> 
> There is a world of difference between a polite request for more information (although I gave you
> everything I had), and fobbing someone off with a story about cosmic rays.
> 
 Chris,

 I doubt there was a single version of the kernel which ever worked
well for all its users.  In a production environment, reverting to an
older version may be the best short-term answer, but if nobody
recognises the problem you won't get any closer to a proper fix.  At
the moment, you have a problem that nobody recognises.  If you're not
willing to test if the problem happens repeatably, (you appear to
have had one failure and immediately reverted to an old kernel), who
do you think will be able to fix it?  And if it turns out it doesn't
fail repeatably, maybe the responses you've received could be
correct.

 The stable team are only there to maintain the current release of
the kernel.  There is no maintenance of earlier releases (except
Adrian's work on 2.6.16), other than what a distro chooses to do to
backport fixes.  Of course, if the problem _is_ reproducible on your
machine and config, you might get asked to try to identify when it
got introduced (e.g. was 2.6.19 itself, or an arbitrary 2.6.19-rc,
ok?).

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

  reply	other threads:[~2007-01-25  1:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2007-01-24 15:06 Chris Rankin
2007-01-24 15:40 ` Hugh Dickins
2007-01-24 13:30 Chris Rankin
2007-01-24 14:37 ` Hugh Dickins
2007-01-22 22:13 Chuck Ebbert
2007-01-23  0:23 ` Jesper Juhl
2007-01-23 20:33   ` Chuck Ebbert
2007-01-23 20:56     ` Adrian Bunk
2007-01-24  4:50   ` Daniel Barkalow

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=20070125010020.GB26654@deepthought \
    --to=zarniwhoop@ntlworld.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrustad@gmail.com \
    --cc=rankincj@yahoo.com \
    --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).