From: Andrew Morton <akpm@digeo.com>
To: thunder7@xs4all.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.59 won't boot, 2.5.58 will, how to I use bitkeeper to get 'in between' ?
Date: Wed, 5 Feb 2003 22:23:50 -0800 [thread overview]
Message-ID: <20030205222350.77e50934.akpm@digeo.com> (raw)
In-Reply-To: <20030206060742.GA6458@middle.of.nowhere>
Jurriaan <thunder7@xs4all.nl> wrote:
>
> 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?
>
I've been regularly snarfing the rollups from
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/
for this very purpose.
Over at http://www.zip.com.au/~akpm/linux/patches/2.5/x/
You will find 15 patches, spread across the lifetime of the 2.5.58->2.5.59
cycle.
If you can identify which of those patches introduced the failure...
next prev parent reply other threads:[~2003-02-06 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 6:07 2.5.59 won't boot, 2.5.58 will, how to I use bitkeeper to get 'in between' ? Jurriaan
2003-02-06 6:23 ` Andrew Morton [this message]
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=20030205222350.77e50934.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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.