From: Dan Kegel <dank@kegel•com>
To: linuxppc-dev@lists•linuxppc.org
Subject: Retrieving linuxppc_2_4_devel corresponding to 2.4.19?
Date: Tue, 18 Feb 2003 16:44:44 -0800 [thread overview]
Message-ID: <3E52D37C.3010608@kegel.com> (raw)
What's the best way to retrieve linuxppc_2_4_devel as of
2.4.19? Browsing through http://ppc.bkbits.net:8080/linuxppc_2_4_devel
I see that the right changeset appears to be 1.1091.1.23
(Lord only knows what those numbers mean):
> ChangeSet@1•1091.1.23, 2002-08-03 16:26:58+10:00, paulus@samba•org
> Merge samba.org:/home/paulus/kernel/linuxppc_2_4
> into samba.org:/home/paulus/kernel/linuxppc_2_4_devel
The magic recipe we receved from the gods to retrieve that version is
ver=1.1091.1.23
bk clone -r$ver bk://ppc.bkserver.net/linuxppc_2_4_devel linuxppc_2_4_devel-$ver
cd linuxppc_2_4_devel-$ver
find . -type d -exec bk get {} \;
find . -name SCCS -print | xargs rm -rf
rm -rf RESYNC/
rm -rf PENDING/
rm -rf BitKeeper/
rm -f ChangeSet
That seems to work. However, I'm a bit concerned for several reasons:
0. it looks pretty hacky
1. there's no label on the changeset in question
2. Tom Rini said:
"... keep in mind that revision numbers are not constant, only TAGs,
and keys. Poking in the BK help should tell you how to go from
a rev to a key, and then back."
So I'm afraid that magic 1.1091.1.23 is going to get renumbered
sometime, and I'll have no way to retrieve a 2.4.19 that
works on ppc405. Poking around on bitkeeper.com's online
doc revealed no discussion of "keys", so I'm a bit mystified.
Can the list comment on the recipe I use to
retrieve a clean kernel source tree, and
on what the heck Tom Rini was talking about
with converting from a rev to a key and back?
Also, I see from the bitkeeper logs that linuxppc_2_4_devel
gets merged into from both linuxppc_2_4 and Linus's tree.
Am I right in assuming that I still want linuxppc_2_4_devel
for ppc405 support?
Thanks,
Dan
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-02-19 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 0:44 Dan Kegel [this message]
2003-02-19 17:39 ` Retrieving linuxppc_2_4_devel corresponding to 2.4.19? Tom Rini
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=3E52D37C.3010608@kegel.com \
--to=dank@kegel$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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