On 5/23/07, Simon Berry <email@example.com> wrote:
> >> I would like to know if it is possible for tortoisesvn to check the
> server for updates, but NOT download the latest updates - only display a
> different overlay if the file is 'out-of-date'.
> >> At present, my working copy has a 'normal' overlay, even if the server has
> a more recent version of the file. I can perform a 'check for modifications'
> command, but this lists the out-of-date file in a dialog - and I would
> prefer this to cause an overlay change.
> >Simon, think what you're asking here. Subversion/TortoiseSVN is designed to
> work offline without a permanent connection to the server. Communication
> with the server is only initiated upon user request.
> >To display such an overlay icon would require TortoiseSVN to poll the server
> in regular intervals, which is IMHO not a good idea.
> >If you want to be informed about changes to the repository, install a
> post-commit hook, that sends an e-mail, an IM message or updates a rss feed.
> What's so bad about using the "check for updates" dialog?
> >About additional overlay icons read: http://tortoisesvn.net/node/3
> Lübbe, Andy
> As a bit of background to my original question, we are using subversion to version large database files (>300MB). Subversion works beautifully - but the updates do take a while.
> For this reason it would be nice for our users have an automatic visual of the files that are out of date - so they can decide if they want/need to update them. The checking process does not have to happen regularly (say on startup & once per hour).
> We find, especially with new users that they assume a 'field of green ticks' means that everything is up to date. I understand this is a matter of properly educating the users, but this can sometimes take a while to sink in (our users are not programmers / highly skilled / highly intelligent).
I'd recommend educating them on the Check for Modifications dialog,
and encourage them to use it before any updates. You could even
configure their systems to not show Update on the main context menu,
and instead show Check for Modifications there.
Check for Modifications also shows all file locks, which are again
only visible if you poll the server. So if you're using locking at all
in your repository, it's a good habit to get into.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed May 23 15:59:06 2007