From: "Neil Wilson" <nwilson@airspan.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: linuxppc_2_4_devel bitkeeper versions
Date: Wed, 16 Oct 2002 18:57:44 +0100 [thread overview]
Message-ID: <001301c2753d$883625a0$31a2883e@m5axc> (raw)
Hi,
I sent this to the bitkeepers list but should probably have sent it here
instead....
I am a bit confused about how to retrieve the exact version of kernel that I
want, I am looking for linuxppc_2_4_devel with the platform support for the
2.4.18 release. I have looked at the changeset summaries via the web
interface and tried to retrieve versions based on bk clone -rX
bk://ppc.bkbits.net/linuxppc_2_4_devel linuxppc_2_4_devel where X has been
v2.4.18, 1.2.2.131, 1.899, 1.900, 1.118.1.470 etc, basically all the rev
numbers surrounding the tag v2.4.18, yet I cannot seem to find the exact one
that gives me release 2.4.18 + platforms.
Am I doing anything obviously wrong or could some kind soul give me the
correct rev number to clone from, please ?, thanks.
Neil
--
Neil Wilson
Airspan Communications Ltd.
Cambridge House, Oxford Road,
Uxbridge, Middx, UB8 1UN, UK.
Tel: +44(0)1895-467265
nwilson@airspan.com
www.airspan.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-10-16 17:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001301c2753d$883625a0$31a2883e@m5axc' \
--to=nwilson@airspan.com \
--cc=linuxppc-embedded@lists.linuxppc.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