Issue 198: Wish: propagate w/o commit

Reported by Dirk Heinrichs, Nov 11, 2011

As it is now, mtn propagate automatically commits the result to the 
database. This is suboptimal, because there's no chance of verifying 
the result prior to commit.

So, something like prop_into_workspace would be nice, where 
workspace contains a checkout of the destination branch.



Comment 1 by Stephen Leake, Jun 23, 2012

how is this different from the existing merge_into_workspace?

Comment 2 by Dirk Heinrichs, Jun 24, 2012

Hmm, didn't even know it existed. However, it takes a revision 
number, not a branch name, like propagate does.

Comment 3 by Stephen Leake, Jun 24, 2012

A branch name is just a way to specify a revision; it means the head 
revision of the branch. For a revision argument, you can use a 
selector to get the same thing: h:<branch>

Comment 4 by Stephen Leake, Jun 24, 2012

One difference is you don't get the conflict resolution machinery 
with merge_into_workspace.

Comment 5 by Stephen Leake, Aug 25, 2012

Status: WontFix

Created: 12 years 19 days ago by Dirk Heinrichs

Updated: 11 years 3 months ago

Status: WontFix

Followed by: 1 person


Quick Links:    -     Downloads    -     Documentation    -     Wiki    -     Code Forge    -     Build Status