Re: Maintaining 'stable' and 'development' versions of a repository (hopeless newbie question)

> You raised a very important issue (IMHO), in which bitkeeper does actually have
> a weakness - at least, it is not totally intuitive how to achieve the desired
> mode of operation. The problem is, that if you have three changesets B, C and D
> (as an example) in the development branch, with D being the latest, and the
> stable branch is at changeset A, you can not pull over changeset D without
> pulling B and C at the same time. Such a thing would be called "cherry-picking",
> and is a feature which is planed for future bitkeeper versions, IIRC.
>

I think you can do a limited form of "cherry-picking" by exporting
changeset D from the development branch, to a patchfile, and then
importing that patchfile into the stable branch.

--Mike