Greg Hudson wrote:
Eric Gillespie wrote:
Yes, i like that. So if i think there is a new config file that
i don't see in my .subversion dir, i can run 'svn setup' or
something to copy in any misisng files (and of course it can just
overwrite the old README). I think that addresses the concerns
about not being able to install new files.
+1
-0.5 on adding a new command for this purpose. Commands are a precious
commodity. Some other revision control systems have triple-digit
numbers of commands, and that can make for a very steep learning curve.
We have 27 commands by my count, which is much better. (I can imagine
condensing that list a bit with a lot of work: svn cleanup would go
away if we had a better wc design; svn info might be collapsed into an
svn status option.) Subversion is not about its dotfiles and should
not have a command which is about playing with dotfiles.
Sorry, forgot how specific everything this list had to be.
+1 on having some way to tell subversion to recreate the .subversion
directory/files. Default to leaving it alone if its already there.
-1 on adding a new command for this purpose. I think an option is
better. Of course, we now have to have the option letters are a
precious commodity argument but there you go.
Mix.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:18:21 2006