[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: READ ME: working copy ickiness!

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2003-01-14 22:49:23 CET

John Barstow <John_Barstow@gfsg.co.nz> writes:
> Just because it's difficult doesn't mean it won't happen. Some development
> environments helpfully ask you if you want to override read-only protection
> when you save a file.
> But if I'm working on a 5,000-file project and the text-base of, say, 100
> files is corrupted, shouldn't I have the option of forcing a refresh of the
> text-base from the server, rather than a)fresh check-out or b) attempting to
> figure out what, exactly, is wrong?


Agree that such a command would be good

   svn repair ?
   svn refresh ?
   svn restore ?

I don't think it blocks 1.0, but patches welcome... (May I suggest
that it be implemented *after* checksums are done, so we'll
automatically verify that the repair is correct?)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 14 23:35:33 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.