#
#
# patch "wiki/BranchUI.mdwn"
#  from [c2e8eeaba3dbca67c08498f78b6c570e2e7e580b]
#    to [1868cfe97cc091afdfd7cc05ecfd7cb1bb667bea]
#
============================================================
--- wiki/BranchUI.mdwn	c2e8eeaba3dbca67c08498f78b6c570e2e7e580b
+++ wiki/BranchUI.mdwn	1868cfe97cc091afdfd7cc05ecfd7cb1bb667bea
@@ -1,10 +1,12 @@
-[[!tag migration-auto]]
+[[!tag migration-done]]
 
 # Idea 1
 
 Have a command "branch".  Usage:
+
   * `monotone branch foo.bar`: switch working copy to be foo.bar (simply modifies MT/options).
   * `monotone branch -r REV foo.bar`: mark rev REV as being in branch foo.bar (simply issues a branch cert)
+
 Make `monotone commit` no longer accept a -b switch.
 
 In all cases give the user feedback on whether they have created a new branch or not.
@@ -16,9 +18,11 @@ Some user experience:
 # Idea 3
 
 Some user experience:
-  http://xaraya.com/pipermail/xaraya_devel/2006-January/002512.html
 
+>  <http://xaraya.com/pipermail/xaraya_devel/2006-January/002512.html>
+
 Perhaps we should provide a `switch` command, which is similar to `update`, but:
+
   * requires a branch argument
   * if that branch exists, does `update -b BRANCH -r h:`
   * if not, switches the working copy to be on BRANCH