From: Nick Warne <nick@linicks.net>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
Jesper Juhl <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.14.5 to 2.6.15 patch
Date: Wed, 4 Jan 2006 19:53:15 +0000 [thread overview]
Message-ID: <200601041953.15735.nick@linicks.net> (raw)
In-Reply-To: <200601041834.23722.s0348365@sms.ed.ac.uk>
On Wednesday 04 January 2006 18:34, Alistair John Strachan wrote:
> On Wednesday 04 January 2006 17:39, Nick Warne wrote:
> > On Wednesday 04 January 2006 17:36, Randy.Dunlap wrote:
> > > > I went from 2.6.14 -> 2.6.14.2 -> .2-.3 -> .3-.4 -> .4-.5
> > >
> > > and how did you do that?
> > > Noone supplies such incremental patches AFAIK.
> >
> > Yes, I got from kernel.org - I am _not_ that clever to devise my own
> > incremental patches, otherwise I wouldn't be asking stupid questions...
>
> Nick's right, both are provided automatically by kernel.org.
Anyway, I started from scratch - 2.6.14, patched to 2.6.15 and then make
oldconfig etc.
I think there needs to be a way out of this that is easily discernible - it
does get confusing sometimes with all the patches flying around on a 'stable
release'.
Nick
--
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb
My quake2 project:
http://sourceforge.net/projects/quake2plus/
next prev parent reply other threads:[~2006-01-04 19:54 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 [this message]
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
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=200601041953.15735.nick@linicks.net \
--to=nick@linicks.net \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=s0348365@sms.ed.ac.uk \
/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.