> A periodically updated icon saying "file not locked" gives
> you a false sense of security. If the periodicity is 1 hour,
> the icon may be wrong for 59 minutes and you could loose
> hours of valuable time on e.g. binary artwork.
If a user cannot accept n-1 minutes of granularity on the icon, they can
check for modifications manually, or decrease n.
> For an offline-usable version control system like Subversion
> the needs-lock approach is quite a good solution for
> non-mergeable files.
> And for mergable files there is no real need for locks.
Although it is not strictly critical to have locks on mergeable files,
it is easier to avoid a merge than it is to perform a merge.
Also, the binary separation of "mergeable" and "unmergeable" is not
accurate. Many source files, such as .c files, might be called
"mergeable" but not always easily mergeable. For example, if a user
changes the name of a function or a class. It is easier to avoid a
merge than it is to perform a merge.
> > For that matter, to my knowledge there is no way to silently
> > periodically get updates either.
>
> You can use the command line client for silent periodical updates.
Perhaps I missed something. The document I looked at was Appendix C.
Automating TortoiseSVN
It says to use something like this:
TortoiseProc.exe /command:update /path:"c:\svn_wc\" /notempfile
/closeonend
When you run this command, a window pops up momentarily, and it will
stay if there was an error. This is not silent, and not suitable for a
periodic background check, for example, incase the network is down.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Apr 24 19:11:49 2006