All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jurriaan Kalkman" <Jurriaan.Kalkman@zrt.nl>
To: <joel.soete@freebel.net>, <parisc-linux@lists.parisc-linux.org>
Cc: <JSO@EUROPAY.COM>
Subject: Re: [parisc-linux] How to merge Kernel 2.4.9 for hppa and new kernel 2.4.10
Date: Wed, 26 Sep 2001 08:16:49 +0200	[thread overview]
Message-ID: <sbb19279.048@ms-zrt1> (raw)

>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

which is something I wouldn't want to do :-)

If you read the linux-kernel mailing list, you'll see that some people =
claim=20
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.

Good luck,
Jurriaan

             reply	other threads:[~2001-09-26  6:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26  6:16 Jurriaan Kalkman [this message]
2001-09-26 18:27 ` [parisc-linux] How to merge Kernel 2.4.9 for hppa and new kernel 2.4.10 Andrew Shugg
  -- strict thread matches above, loose matches on Subject: below --
2001-09-25 16:07 Soete Joel

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=sbb19279.048@ms-zrt1 \
    --to=jurriaan.kalkman@zrt.nl \
    --cc=JSO@EUROPAY.COM \
    --cc=joel.soete@freebel.net \
    --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 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.