Eric Hanchrow wrote:
>>>>>> "Max" == Max Bowsher <maxb@ukf.net> writes:
>
> Max> First, I think that, if necessary, we should make the
> Max> description of what "svn revert *is* clearer, rather than
> Max> starting to describe what it is *not*.
>
> That would be fine ;-)
>
> Max> Second, that's a horrible way to delete files not under
> Max> revision control. It wastes time and bandwidth, and doesn't
> Max> let you keep local mods whilst doing so.
>
> True, it's inefficient. And I know it doesn't let you keep local mods
> -- that's the whole point: I'm trying to describe how to restore a
> working copy to its "pristine" state.
>
> Max> Just use a tiny bit of shell script joining "svn st
> Max> --no-ignore", sed and rm.
>
> I know that and you know that, but I'm afraid some users of Subversion
> don't want to deal with shell scripting. I know this for a fact,
> since one of those users (a co-worker: I just switched my workplace
> over to Subversion this week) came to me and said "I accidentally got
> all these extra files in my working copy; how do I get rid of them? I
> tried `svn revert' but that didn't work". He doesn't want to learn
> shell scripting; he just wants to get his working copy back the way it
> was before he screwed it up.
>
> So I'm trying to describe a way to solve his problem. Perhaps the
> `svn revert' section isn't the right place for this information, but
> since he mistakenly tried `svn revert', I figured it was as good a
> place as any.
I'm not sure where - maybe one of the book authors could inject an opinion
here?
Perhaps the problem would be solved best by adding a 'svnpurge' script to
tools/client-side ?
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 3 00:11:36 2004