> Well, locking is an upcoming feature, so that should settle
> their concerns.
A locking mechanism is the initial, obvious, short-sighted solution to the
problem of concurrent development. A little bit of experience with the
merging approach, as implemented in subversion, should be enough to convince
anyone that this solution is vastly superior.
Locking should only be used on unmergable files. Some managers, lacking
understanding, will undoubtedly dismiss merging as hopelessly complex and
error-prone, and require locking for all files. The rest of us can sit back
and watch their productivity spiral down the drain, then laugh loudly and
wink at one another when they report that Subversion isn't a very good tool.
A guy came to the hardware store to report that his new chainsaw wasn't
working out, and wanted to return it. "It's too heavy, and just doesn't cut
as well as my old saw," he said. "It took me over an hour to cut down one
small tree." The store owner was surprised, and said, "That's terrible!
Let's check it out, something must be wrong." He flipped the switch, pulled
the cord, and the saw roared to life. The customer jumped back and looked
aruond wildly. "What's that noise?!?"
;)
--- Eric Wadsworth
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 7 04:39:30 2005