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

Re: Track changes

From: Robert Schneider <R.Schneider_at_weingartner.com>
Date: 2007-10-17 14:55:52 CEST

> > However, not all projects are developed by thousands of people. I
guess
> > most projects have only few developers, and likely they are within a
> > LAN.
>
> Most? How can you say that? Have you done a survey?

I assumed an exponential distribution about the developers per server or
repository. Might be wrong, I know.

>
> It has already been considered many times, this is not a new idea.
>
> Changing the overlay to red when there are repository changes would be
> a bad idea for several reasons:
> 1. TortoiseSVN only contacts the repository on request. That is a key
> feature of subversion and allows you to continue working while you or
> the repository are offline.

So what? Many applications works like this. If the connection or the
server is down then the feature is currently just not working. That's
all. I regard the auto-check feature as a little helper, not as a
reliable thing where you get a message box saying 'the server is not
accessible, cannot continue, ...'.

> 2. How do you distinguish between local and remote changes?

Take another indicator, i.e. svn status column or an extra column. It
doesn't have to be a red icon. Or it could be a black one, or purple or
whatever.

> 3. The indication would immediately be out-of-date. You cannot poll
> the repository every second, so whatever interval you choose gives a
> window where your WC does not necessarily reflect the true remote
> status.

It doesn't have to be seconds. Let's think about minutes.

> 5. If we make this an option, lots of people will think "Ooh, that's a
> nice idea" without also thinking of the load on public servers.

You could document the issue or give a hint if the feature gets enabled.
Besides, maybe some tsvn properties could be installed to disable the
feature by default for a repository.

Just think about a few developers in a LAN with some svn repositories.
There should be no problem if the svn server gets polled every minute.
For this scenario the auto-check feature might be appropriate. At least
it wouldn't be a problem. Right?

Finally: It would just be nice to see track changes of the repository
without setting up a complex machinery. Do you know what I mean?

But if you still think it is not a good idea (even though the idea is
not new) then don't implement it. Naturally, it's up to you. Don't get
me wrong: I like TortoiseSVN.

Cheers,
Robert

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Oct 17 15:16:53 2007

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

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