Ben Collins-Sussman wrote:
> Vincent Starre wrote:
>
>> My main problem with svn cp and import commands are the lack of a way to
>> see what the tree will look like before and after an operation, without
>> actually performing the operation.
>
>
> So what do you recommend? How would you improve things?
>
>
I feel that absolutely everything should take --dry-run, even things
where it doesnt seem to make sense :)
-------------------------------------------------------
C:\>svn import c svn+ssh://deknez/r3wt/svn/tst/branches/c -m ""
Log message unchanged or not specified
a)bort, c)ontinue, e)dit
c
Adding c\a
Adding c\b
Adding c\c
Adding c\d
Adding c\d\e
Adding c\d\f
Committed revision 14.
-------------------------------------------------------
This tells you which local files were committed, but makes no mention of
the remote structure-
for example "tst" did not previously exist.
meanwhile, this command evidences the need for a "dry run".
C:\>svn import c svn+ssh://deknez/r3wt/svn/tst/branches/ -m ""
if "branches" already exists, this creates 'c' under 'branches.
otherwise, it creates only 'branches'.
Similar to a normal system "cp", only creating any extra directories
along the way.
Yes, everyone learns to deal with it as they use it, but offering a
better way
to avoid worthless oops commits, for those first starting, is always a
good thing. And, of course,
some of us have alias rm='rm -i' in our .profiles even after years of
experience- it's nice to get an
"are you sure?" sometimes.
On a related note, it seems that svn cp does /not/ create leading up
directories. it is not entirely
unoften that I am put off by needing an extra mkdir commit to create a
"tags" directory. (of course
everyone just tells me "plan ahead")
in short: warnings = GOOD, errors = Annoying! ;)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 5 23:43:01 2005