RE: Backing out Subversion?

> Since we support a large manufacturing floor/sales team/etc., deleting
> the production code and doing an "svn export" isn't an option.

Strange enough.

> My best thought was to recursively drill through all subdirectories, deleting
> the .svn dirs--which would be a rather ugly manual process, I think.

What's wrong with

  find -type d -name .svn rm -rf {} \;

?

It is certainly a 'less manual process' than typing in a whole mail ;-}

> 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?

Something like

  for i in `svn log foo.sql | grep '^r' | cut -d ' ' -f 1` ; do
    svn cat -$i > foo.sql.$i
  done

should do the trick. [This is untested, so try out in a quite corner...]

 
> 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...

There is no such problem as far as I can tell.

Andre'

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 2 10:43:06 2005