Thomas Harold <tgh@tgharold.com> wrote on 11/02/2006 01:30:03 PM:
> Probably one of the more annoying errors that SVN gives. Basically, if
> you start to update a large directory (or directory tree) and stop the
> update somewhere in the middle, SVN now doesn't know what to do. Any
> further attempts to "svn up" on the tree will fail with the "already
> exists" error.
>
> There has to be a more graceful way of handling this failure. Besides
> requiring the user to blow away all of the data (a few GB in some cases)
> that they've already downloaded and re-pull everything down over the
wire.
>
> If the CRC / checksum / MD5 of the file matches what is already in the
> repository, SVN should simply note the fact, not transfer the file, but
> mark it as being under version control.
>
> (I realize this is probably in a bug or enhancement request... so I'm
> probably just venting.)
Subversion trunk, which will eventually be 1.5, has enhancement to
update/checkout/switch to allow them to continue when encountering an
existing file. I believe you have to specify the --force switch on the
command to get this feature. Basically, it will leave the local file in
tact and just slide the working copy file beneath it. If the files are
different svn status will show the file as locally modified, revert would
restore it to the repository file.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 2 19:37:18 2006