From: Grant Coady <grant_lkml@dodo.com.au>
To: Nick Warne <nick@linicks.net>
Cc: Greg KH <greg@kroah.com>,
Alistair John Strachan <s0348365@sms.ed.ac.uk>,
"Randy.Dunlap" <rdunlap@xenotime.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: Thu, 05 Jan 2006 09:49:45 +1100 [thread overview]
Message-ID: <esjor11m4qu0tob1efjsebj10e5caeuu38@4ax.com> (raw)
In-Reply-To: <200601042220.59637.nick@linicks.net>
On Wed, 4 Jan 2006 22:20:59 +0000, Nick Warne <nick@linicks.net> wrote:
>On Wednesday 04 January 2006 22:15, Greg KH wrote:
>
>> > 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!
>>
>> That's because 2.6.15 is the latest stable release.
>>
>> > OK, I suppose we are all capable of getting back to where we are on
>> > rebuilding to latest 'stable', but there _is_ a missing link for somebody
>> > that doesn't know - and I think backtracking patches isn't really the way
>> > to go if the 'latest stable release' isn't catered for.
>>
>> Um, it is, see my sentance above. And if you want to download older
>> stable releases, you can jump to the proper directory, how long do you
>> want us to put older stable releases on the main page for? :)
>
>OK, I see what you mean, but 2.6.14 wasn't the latest 'release' - 2.6.14.5 was
>(according to kernel.org). Yet there is no upgrade path for that build (or
>any other .x releases)
>
>It is a bit of a mess really.
Nah, search the archives for 'sucker tree' -- was much worse before
we have the stable bugfix patchlets in between the main kernel
releases, there was never going to be a 2.6.X.Y to 2.6.X+1 patch as
mainstream kernel development may fix issues entirely differently.
Kernel development is an ongoing process, the stable trees are
temporary branches outside of (or beside) mainstream development,
that easier for you?
Grant.
next prev parent reply other threads:[~2006-01-04 22:49 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 ` 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 [this message]
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
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 20:10 ` Matan Peled
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=esjor11m4qu0tob1efjsebj10e5caeuu38@4ax.com \
--to=grant_lkml@dodo.com.au \
--cc=gcoady@gmail.com \
--cc=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