> From: Simon Large:
> > The new lock feature is just perfect except one little detail: we
> > have the sourcecode of our small projects sorted in subfolders like
> > "inc", "src", "doc" etc....
> Why must you get a lock? src and inc sound like typical source file
> folders for text-based stuff. You don't need to use locking for that.
> Have you come from VSS or similar?
For heavens sake, no! I would use that only over my dead body ;)
My senior wanted something like the locking feature so that you (and especially he) could see who is working on what.
The department I am working in consists of five people, me and my senior included. We are spread over our company site and often do not see each other the whole day. It is a bit of a problem to coordinate work on different problems.
Locking even the sourcefiles forces us to ask what the other is doing right now, thus hopefully preventing to work on the same problem. Well, I am new around here and that is how I understand it was meant to be.
> > It would be nice if you could get the lock for a lot of files in
> > different subfolders by right-clicking the parent folder and
> > selecting "get lock...". Then you could lock the whole project and
> > work on it.
> That would be very anti-social. Then none of your co-workers could do
> any work anywhere in the project. The Subversion project has
> many people
> working on it and they do not use locking at all. It is
> really intended
> for use on unmergeable files, like graphics files.
We have a big number of small projects, script software to control our measuring machines. We use a shared lib everyone can expand. I think it is better to use the lock here. If you need a quick extension to the lib to do some evaluation calculations and you see the file is locked than you can ask your co-worker if he had the same idea and is already implementing the function.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jun 6 11:22:25 2005