Re: Repeated merge strategies

Zack wrote:
> I suspect that the second most common repeat-merge situation does
> require ancestry sets -- you've got a development and a release
> branch, a few individual patches have been pushed from dev to rel,
> and now you want to merge the entire dev branch to release.

Wait a minute. Wouldn't this operation be better handled by creating a
new release branch off the mainline? Or, barring that, dumping the
contents of the mainline onto the release branch instead of doing a
merge?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 22 08:15:06 2002