BitKeeper on IA64
(This information is now mostly obsolete, as the standard 2.6 tree now runs on IA64 without patches. Quilt or similar are still useful to keep the quick-fix changes to get a tree snapshot running and the changes you're actually working on separate).
See also Tony Luck's article on the various available trees, at http://www.gelato.unsw.edu.au/linux-ia64/0408/10621.html
Linus's BK trees didn't use to run on IA64 without patches.
David Mosberger didn't use to maintain a usable cloneable tree. (He does now: http://lia64.bkbits.net:8080/linux-ia64-2.5 )
This means that you're going to have to edit in several places, and not get confused, in order to develop using BK on IA64.
The easy way to do this now is to use Quilt
The important trees are:
David's to-linus tree that contains all the changes he expects Linus eventually to take up. It can be cloned from http://lia64.bkbits.net:8080/to-linus-2.5 This will also contain all the changes in Linus's tree up to that last time David merged it.
Linus's 2.5 tree, that contains changes from everywhere, including changes from the to-linus tree as of the last time Linus merged it. This tree is at http://linux.bkbits.net:8080/linux-2.5
- Your own development trees.
To release patches to the general Linux community, you'd better be generating diffs from Linus's tree. To send patches to David Mosberger, the IA64 2.5 developer, the patch has to be generated from a merge tree consisting of Linus's tree with the patch from http://www.kernel.org/pub/linux/kernel/ports/ia64/2.5 (or one of its mirrors), together with the patches in the to-linus tree.
Keeping the stuff you're working on separated from the other changes requires constant attention to detail and discipline.
I used to maintain a snapshot merge copy at bk://gelato.unsw.edu.au:2020 that consists of Linus's tree patched with David's patch and merged with the to-linux tree, with changes as necessary to cope with minor differences between the trees. This tree is no longer kept up to date.
A Maze
