Re: revert --force

On Thu, Dec 10, 2009 at 04:52:55PM +0100, Tobias Hahn wrote:
> Here's my use case:
> - I'm working on a branch.
> - I have a path in my working copy which is modified by some automatic scripts.

This is not a great practice. Can you instead generate the modifications
somewhere else, such as into a directory which you svn:ignore?

> - About once a week, I merge trunk. To do so, I need a clean working copy. To get it clean, I have to
> - manually delete all these files (slow and error prone) or
> - delete the path and checkout again (very slow)
> - just revert --force it (wishful thinking).

Rather than blowing everything away and checking out again, I use
something like this to clean up before a merge:

svn status | grep '^?' | awk '{print $2}' | xargs rm -rf

I don't disagree that revert --force might be handy, but there are
probably a number of reasons why that was deemed too scary for prime
time.

tyler

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2429242

Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-12-10 17:45:25 CET