My team has been reluctant to adopt subversion (old habits, etc.); one
concern that was brought to my attention today is, "if we set this up,
and put the production code under version control, and in a couple of
weeks decide that it's not working/we hate it/whatever, is it possible
to back out of it--or are we stuck using it?"
Since we support a large manufacturing floor/sales team/etc., deleting
the production code and doing an "svn export" isn't an option. My best
thought was to recursively drill through all subdirectories, deleting
the .svn dirs--which would be a rather ugly manual process, I think. Is
there a better way?
Also, is it possible to get a dump of the files as they've changed
within the repository? That is, if a file ("foo.sql") was changed in
revisions 2, 5, and 9, we'd like to have foo.sql.2, foo.sql.5, and
foo.sql.9. Is there some easy way to get this information from
subversion for an entire repository, or would we have to create some
sort of script to do it?
Naturally, I *don't* want to do either of these, but some of the people
in the team would be more willing to try the system if they knew they'd
be able to back out if need be...
Thanks,
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 1 23:42:10 2005