From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Steven Cole <elenstev@mesatop.com>
Cc: Alan Cox <alan@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.64-ac1
Date: 06 Mar 2003 22:51:16 +0000 [thread overview]
Message-ID: <1046991076.17715.129.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <1046985881.4992.99.camel@spc9.esa.lanl.gov>
On Thu, 2003-03-06 at 21:24, Steven Cole wrote:
> I backed out the same partitions stuff as before, and 2.5.64-ac1 boots
> fine. This is the resulting diff.
Backing it out isnt an option in the end, it has to get fixed 8(
next prev parent reply other threads:[~2003-03-06 21:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 19:15 Linux 2.5.64-ac1 Alan Cox
2003-03-06 19:56 ` [patch] 2.5.64-ac1: fix apic.c compile Adrian Bunk
2003-03-06 21:24 ` Linux 2.5.64-ac1 Steven Cole
2003-03-06 22:51 ` Alan Cox [this message]
2003-03-06 22:58 ` Andries Brouwer
2003-03-06 23:03 ` Steven Cole
2003-03-07 0:10 ` Alan Cox
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=1046991076.17715.129.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=elenstev@mesatop.com \
--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;
as well as URLs for NNTP newsgroup(s).