Updated Issue 198 - Wish: propagate w/o commit (monotone)

Hello,

The following issue has been updated:

198 - Wish: propagate w/o commit
Project: monotone
Status: WontFix
Reported by: Dirk Heinrichs
URL: https://code.monotone.ca/p/monotone/issues/198/
Labels:
 Type:Defect
 Priority:Medium

Comments (last first):

# By Stephen Leake, Aug 25, 2012:



 Status: WontFix

# By Stephen Leake, Jun 24, 2012:

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

# 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>

# 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.

# By Stephen Leake, Jun 23, 2012:

how is this different from the existing merge_into_workspace?

# 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.

Thanks...

    Dirk



--
Issue: https://code.monotone.ca/p/monotone/issues/198/