From: Soete Joel <joel.soete@freebel.net>
To: Jurriaan Kalkman <Jurriaan.Kalkman@zrt.nl>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] How to merge Kernel 2.4.9 for hppa and newkernel 2.4.10
Date: Wed, 26 Sep 2001 15:47:35 +0000 [thread overview]
Message-ID: <3BB1F897.F11FCE7E@freebel.net> (raw)
In-Reply-To: sbb19279.047@ms-zrt1
Jurriaan,
Jurriaan Kalkman wrote:
>
> >Hi all,
> >
> >I just learn that new release 2.4.10 of GNU/linux kernel was released.
> >I am curious to know how to merge last kernel 2.4.9-paxx and the new
> >2.4.10?
> >Is somebody can explain me or where to find relevant info?
> >
>
> - get a plain 2.4.9 source tree
> - make a diff between 2.4.9-paxx and 2.4.9
> - download the 2.4.9-2.4.10 diff
> - apply to the 2.4.9 sourcetree and create a 2.4.10 sourcetree
> - apply 2.4.9-paxx diff to 2.4.10
>
> which should all be straight-forward, but then
> - solve all the .rej files that are created, and debug the new kernel
Actually I was not so far from the solution; I start this method
(basicaly on vger cvs 2.4.10-prexx) and I just miss the last two steps.
Thanks a lot.
>
> which is something I wouldn't want to do :-)
>
> If you read the linux-kernel mailing list, you'll see that some people claim
> 2.4.10 is the best thing since sliced bread, but the first serious VM problems
> have been sighted already, so upgrading right away is risky.
>
> Eventually, it'll be in the CVS at puffin.external.hp.com. Until then, the best
> thing to do is wait, unless you have the capabilities to debug the last step.
> If so, I think there are other things to get your teeth in - just ask here.
Ok, I am far to have enough kernel knowledge (just a bit c) to begin
this job alone. Also I will follow your advise and wait it puffin CVS.
>
> Good luck,
> Jurriaan
Anyway It could also be helpfull for any other project.
Thanks again,
Joel
parent reply other threads:[~2001-09-26 15:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <sbb19279.047@ms-zrt1>]
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=3BB1F897.F11FCE7E@freebel.net \
--to=joel.soete@freebel.net \
--cc=Jurriaan.Kalkman@zrt.nl \
--cc=parisc-linux@lists.parisc-linux.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