"Sam Washburn" <swashburn_at_inovationeering.com> writes:
> It doesn't even need to schedule it for deletion, just mark it missing. But
> it should not download a new copy. The key is fixing the pristine copy and
> svn can then report the differences as it usually does
>
> I don't think it should be that difficult to implement. Even
> the --metadata-only idea Alan had would be fine. Which, I guess would be
> excluding a piece of code instead of writing something.
>
> Yes, it can happen in many other circumstances than just a fluke networking
> issue. "Listman" mentioned broken tools. That happens frequently for us
> too.
>
> And, imho, it seems a lot more professional for the project to say "run svn
> rebuild" rather than "first delete all your .svn files..."
>
> Well, thanks for considering it. I really like svn. I know others have bad
> things to say about cvs and svn due to frustrating experiences like mine,
> and maybe this would be a step closer to winning them over.
I think we're all in favor of a script to do this. Adding a new
subcommand to svn itself, however, is a large user interface burden, so
we're usually pretty conservative about adding new subcommands.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-01 05:55:17 CEST