On Sat, May 24, 2008 at 12:16 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> "Sam Washburn" <swashburn_at_inovationeering.com> writes:
>> Ryan Schmidt from the users list helped me track down the problem which
>> apparently was that, somehow the pristine version of my local copy was
>> updated, but not the repository. I'm not sure what caused this perhaps it
>> was my then shaky net connection.
>>
>> His recommendation to me was to checkout a fresh copy and manually merge in
>> the changes. Fortunately, this is not a big deal since there were only a
>> couple of small files our of sync.
>
> Well, would it have been a big deal if there were many files out of
> sync? It's a very scriptable task.
>
>> So, my feature recommendation would be something like a 'svn rebuild'
>> command that would re-download and recreate all the .svn dirs and files
>> inside of the working copy *without* modifying anything outside of the .svn
>> (i.e. any local changes).
>>
>> The resulting rebuild would look as if someone checked out a fresh copy and
>> manually made the changes. Files on the repo that are missing from the
>> working copy would be marked as missing, and files on the working copy which
>> are missing from the repo would be marked as unversioned.
>>
>> What do you think?
>
> We could put it in svn, but I'm not sure how often the situation comes
> up, and it's pretty easy to script when needed...
I meant to respond to this.
SVN 1.5 has a feature that gets you most the way there:
svn checkout --force
It does exactly what is asked for, with the exception that I suspect
you should delete all of the .svn folders before running it.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-24 18:18:47 CEST