Bruce Webber wrote:
>
> Somewhere along the line, client 1 should communicate with his team and
> let them all know that he has renamed the file. This is especially true
> if the file is one that more than one person may be working on. A
> version control system cannot replace effective communications.
>
I've never liked this sentiment ever since I first saw it expressed in
Subversion discussions. It's the wrong metaphor for the version control systems.
Instead of characterizing the version control system as a replacement for
effective communications, it should be characterized as an additional
communications channel. After all, that's why so many teams automatically send
email on checkins. Not only that, but it also in a better situation to provide
some particular communications at exactly the point in time when they're most
needed.
The implication is that the version control software has responsibility for
maintaining the fidelity of that channel. So when some does an svn mv, but the
log shows it as a delete and add, it's not that there was no team communication,
but that Subversion introduced static into the communications channel,
damaging the effectiveness. I expect that the task for a "true rename"
operation will fix this, among other things.
Gary
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 7 14:03:41 2005