Nested repositories
Brendan Heading <[email protected]>
| Newsgroups | gmane.comp.version-control.bitkeeper.user |
|---|---|
| Message-ID | <[email protected]> |
On some of the projects I'm working on, the source base is huge and it makes sense to divide it up into several subtrees. For example, in a typical embedded project you might have three trees - one for device drivers and framework stuff, one containing a linux kernel used in the project, and one containing the user space applications. The idea is that a given developer beavering away on applications can just pull down the repository containing the applications, because he doesn't need the kernel or the device drivers. But the build or release manager needs to pull down the entire system and build the whole thing to make a delivery. How do people manage this kind of thing with Bitkeeper ? The idea I have that really would be the icing on the cake would be to have some kind of main repository that exists only to hold sub-repositories. Then people can either clone that main one (in turn giving them all the subsystems) in order to, say, do a full build, or they can clone just the one they need. Brendan _______________________________________________ Bitkeeper-users mailing list [email protected] http://bitmover.com/mailman/listinfo/bitkeeper-users To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.