On Thu, Oct 20, 2011 at 12:47:25PM -0500, Les Mikesell wrote:
> On Thu, Oct 20, 2011 at 12:26 PM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> >
> >>
> >> How is a user supposed to know if his working copy requires cleanup?
> >
> > You'll get E155021.
>
> But only after it is too late, right? Are there any tools to check
> this that don't overwrite the versions that might have still been able
> to do something with the existing working copy?
If a working copy requires cleanup, a 1.6 client that touches the
working copy will tell you so. A 1.7 client will refuse to upgrade it.
> >> And how should it be handled in multiuser scenarios where the svn
> >> binaries are managed and updated by someone other than the people who
> >> may have active working copies?
> >>
> >
> > Have users always run 'svn cleanup' before they leave for the night on
> > any wc's that they ^C'd during the day?
>
> Is that documented somewhere?
I don't think Daniel is right here. Generally, you don't need to run
'svn cleanup' just because you cancel some SVN operation with Ctrl-C.
You need to run it after an svn client has crashed or for some other
reasons failed to clean up its locks or run pending changes from the
working copy's work queue.
Received on 2011-10-20 19:52:30 CEST