From: Jurriaan <thunder7@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: 2.5.59 won't boot, 2.5.58 will, how to I use bitkeeper to get 'in between' ?
Date: Thu, 6 Feb 2003 07:07:42 +0100 [thread overview]
Message-ID: <20030206060742.GA6458@middle.of.nowhere> (raw)
Until now, all 2.5.59-based kernels (2.5.59 vanilla, 2.5.59 + vmlinux
patch, 2.5.59-mm[1-8]) hang very early in the boot-process on my system,
right after 'Uncompressing Linux...'
I am willing to try which patch between 2.5.58 and 2.5.59 caused this,
but I can't find out how to extract these patches. If I browse the
linux-2.5 repository on the web-interface @ bitkeeper, I don't see a
message 'And with this patch-set, we've reached 2.5.58 - any patches
after this apply to 2.5.58 and will create 2.5.59 in due time'.
/usr/src/linux/Documentation/BK-usage/ seems to focus more on uploading
patches. There is something on getting the diff between two kernel
versions, but I need finer patches/revisions/changesets. I can see how
to download the initial tree, but what do I do next?
Thanks,
Jurriaan
--
In case of fire, do not attempt to use lifts.
(To which was added:)
Try a fire extinguisher.
GNU/Linux 2.4.21-pre3-ac5 SMP/ReiserFS 2x2339 bogomips load av: 0.00 0.16 0.16
next reply other threads:[~2003-02-06 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 6:07 Jurriaan [this message]
2003-02-06 6:23 ` 2.5.59 won't boot, 2.5.58 will, how to I use bitkeeper to get 'in between' ? Andrew Morton
2003-02-06 12:33 ` Dave Jones
2003-02-06 12:51 ` Duncan Sands
2003-02-06 12:50 ` Dave Jones
2003-02-07 20:19 ` Jurriaan
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=20030206060742.GA6458@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-kernel@vger.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