On 8/1/06, D.J. Heap <djheap@gmail.com> wrote:
> In what circumstances is your tool used? During a normal user driven
> update or during an automatic process of some kind?
Both. It's usually faster than normal updates, and it detects
immediately if the WC and HEAD are equal, and stops right away, rather
than going through the directory-walk motions. People usually do a
regular full WC update in the morning and during lunch break, a
scheduled update late at night, and do a quick log-list-only update
every other time. It has become our default update method.
> Are you saying you never want the update to stop -- just skip
> problematic files? That seems like a departure from Subversions
> current 'normal' behavior...
I realize that. I guess we don't usually care about that "normal"
behavior in OS-local-lock situations, because they usually arise when
the locked file is being viewed or edited. When the user realizes
this, they either choose to continue what they're doing and update
that part later, or close it and update immediately. In either case,
the subsequent update is always a little faster, so they're happy.
I agree underlying Subversion API should probably just prevent all
updates until all local-lock issues are fixed, for better safety. I
guess, in this one case, our office isn't as concerned about this kind
of atomic version safety.
:) Jared
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 2 05:37:10 2006