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

"Brendan Heading" <[email protected]> Mon, 20 Jun 2005 16:08:26 +0100
Newsgroups gmane.comp.version-control.bitkeeper.user
Message-ID <[email protected]>
Andy Chittenden writes: 

> o	what if the "cherry-picked" patch relies on a small fragment of
> 	one of the "rejected" changesets? You'd then need to either
> 	reapply a portion of one of the patchs for those files
> 	affected as well or change the patch you're applying - I guess
> 	patch would generate .rej files in this case so you knew you
> 	had to do something.

Any given changeset always implies all of the changesets that went before 
it. Even if BK had some fancy extra sugar that made it slightly easier to 
move changesets between different repositories, you would always have to 
deal with the fact that the changeset, removed from it's original context, 
may not necessarily be semantically correct. 

IME, ChangeSets tend to fool people into believing that they can take any 
group of changes in whatever order and apply them one by one in any order to 
get the same effect. Darcs or any other changeset based SCM is going to have 
the same problem.