Re: Communication when using subversion

"Adam Lofstedt" <adaml@visimation.com> writes:
> I want to know how other developers communicate with each other when they
> are using subversion. In particular, I'm curious how when working with
> multiple projects and multiple developers, you communicate the fact that you
> are working on a particular file, without locking in place.

I've been working on a very large project (NetBSD) for about a decade
now using CVS. The answer is, "you don't have to". It never has been a
problem in practice, even with people working on many of the same
files. The tools just do the right thing for the most part.

When I started using CVS, the "no locks" thing freaked me out, but it
turns out it *really* isn't a problem.

> Right now, our devs use VSS (yuck!),

That's your problem right there...

> How is this communicated in the subversion world, if locks are not
> implemented? This is especially important for binary files that can't be
> merged.

If you try to check in a binary file and the version you had checked
out wasn't up to date when you tried to do the commit, you'll be
told. Same for most other files.

Perry

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Feb 21 02:58:28 2004