On the 'move-tracking-2' branch, 'svnmover' now simulates a WC, in
memory. Changes you make are committed when you exit svnmover, or
whenever you use the 'commit' command.
Recently added svnmover commands:
commit # also, in effect, updates to head
update .@REV # the '.@' is required syntax but ignored
status # alias for 'diff .@base .'
revert # revert all changes in the WC
The 'update' command keeps local changes, by attempting to merge them
with the incoming change. However, it doesn't yet handle conflicts (it
bails out part way through the merge).
Simple examples of usage:
[[[
$ svnadmin create repo && ln -s /bin/true repo/hooks/pre-revprop-change
$ svnmover --ui=paths -U file://$PWD/repo
svnmover> mkbranch trunk
A trunk (branch B1)
svnmover> ls .
.
trunk (branch B1)
svnmover> mkdir branches mkdir tags
A branches
A tags
svnmover> status
--- diff branch B0 at /
A branches
A tags
A trunk (branch B1)
--- added branch B1 at /trunk
svnmover> commit
Committed r1:
--- diff branch B0 at /
A branches
A tags
A trunk (branch B1)
--- added branch B1 at /trunk
]]]
Please let me know your thoughts!
- Julian
