From: Cort Dougan <cort@fsmlabs.com>
To: "Conyers, Steve" <steve.conyers@lmco.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Would like to upgrade from 2.2.17 to 2.4 or 2.5
Date: Mon, 7 May 2001 17:12:45 -0600 [thread overview]
Message-ID: <20010507171245.D680@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <64AFDC09F27AD411BA9500508BDF7E3069E2F9@emss08m04.ems.lmco.com>; from steve.conyers@lmco.com on Mon, May 07, 2001 at 04:09:29PM -0700
I can give you a tar file of 2_4_devel or you can pick one up from
ftp.kernel.org/pub/linux/kernel/people/cort/ or ftp.fsmlabs.com/pub/linuxppc/
} Would be happy to upgrade from 2.2.17. Using it (temporarily) cuz we got a
} patch to it from Motorola that "might work" with the MVME5100 board. One of
} your associates (Matt Porter) has indicated that a more mature linuxppc
} already patched for MVME5100 and tested somewhat is under Bitkeeper as
} version 2.5. For various reasons, we can't install Bitkeeper here, so we
} have been pressing on with 2.2.17 with patches and hacks per our
} correspondence. This is how far we get with 2.2.17:
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-05-07 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 23:09 Would like to upgrade from 2.2.17 to 2.4 or 2.5 Conyers, Steve
2001-05-07 23:12 ` Cort Dougan [this message]
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=20010507171245.D680@ftsoj.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=steve.conyers@lmco.com \
/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).