On 10/17/07, braulio.horta@embraer.com.br <braulio.horta@embraer.com.br> wrote:
>
>
> > > No, the icons cannot turn red when the repository changes. That would
> > > mean contacting the repository regularly to check. That means a
> > > permanent network connection is required. now imagine thousands of
> > > developers on the Apache or Gcc projects all doing that simultaneously
> > > and think about the server load ...
> >
> > 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.
> >
> > How much traffic would it be? I don't think that it is much. So why not
> > add this feature as an option that can be turned on or off somewhere?
> > Would be nice if one could see that something has changed.
> >
> > Don't you think that it is considerable?
>
>
> Is it possible (or feasible) add an option for client tell server when
> it started changing a file (like a lock without locking), make
> this information avariable for other people using the same file and, maybe,
> send it for all people working in this file.
That would require Subversion library and server support. And you'd
have to go through all the same steps as you do for a lock - so why
not just use locking (with a post-lock email going out saying "Bob
locked file X at <time"> and post-unlock saying "Bob unlocked file X
at <time>")at that point?
> I think it is a ruge improvement for very big teams.
> Especially for very complex or safe critical applications.
NOTHING replaces developers communicating with one another directly.
If you have people walking all over each other regularly, you need to
restructure your development process (maybe with private branches), or
get people to actually talk to each other.
---------------------------------------------------------------------
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:30:34 2007