Maik Schmidt wrote:
> My superiors demands that the version management we will be using has the possibility to tell the user that a file is in use by someone other.
They've got it all wrong. Subversion does automatic merges, so
there's nothing wrong with two people working on the same file at the
same time. Try it ;-p.
> With (Tortoise)CVS you can activate something like "check out write protected" and then de-protect the files for editing
> -- with that you can see if someone is working with a file.
You could collectively agree to set a 'code:worked-on' property on
each file that you are going to start work on.
Subversion has a 'post-revprop-change' hook, so when you commit the
file with the above property added, a web page that reflects who's
working on what could be automatically updated.
Or you could, as mentioned, wait a month or so for Subversion 1.2.
Probably easier.
The locking code was merged to the Subversion trunk today, so you
could also grab a fresh copy and compile Subversion with locking
yourself, if you dare ;-).
> He doesn't want this lock to be a true lock, he just wants a possibility to see if someone other is working at that file already.
I'll go ahead and grade him with an A-, since he misunderstood the concept.
(Actually, he'll get a B, since forcing people to serialize their
workflow like this is OK for, say, image or other binary files that
are not auto-mergeable. Guess who's been lurking the SVN mailing list
today =).)
If he just wants to be able to overlook who's doing what in the
repository, use Apache as your SVN server. It keeps a nice log on
every little detail that anybody does on the server (including simple
reads and browsing).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Mar 22 19:23:00 2005