[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Communication of CHANGES

From: Harvey, Edward <Edward.Harvey_at_patni.com>
Date: 2007-11-30 02:29:13 CET

> If you expect multiple GUI clients
> to be concurrently running and always display the same info you are
> going to need a lot of synchronization and locking gunk that doesn't
> seem to belong in a core api - and if it doesn't do that, what's the
> point of adding more than you'd get with 'svn -u status >file'?

Regardless of caching, you will have problems if you have a bunch of
clients all modifying stuff in the same directory. Let's operate under
the assumption that somebody will use one client at a time, but they
might switch from client to client, and if they switch from one client
to another, they're smart enough to know they need to refresh their view
in the 2nd client.

So, given: subversion won't do "synchronization and locking gunk." For
various simultaneous clients.

Consider the simple case where a tortoise user modifies some file under
some directory tree. The "locally modified" icon will propagate up its
parents. So it's easy to see at a glance, which files are modified, and
which folders contain modified stuff. The same would be useful to know
about "out of date" files. This does not get accomplished with "svn
status -u > file"

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 30 02:39:58 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.