[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: /#cvs.lock): No such file or directoryctory for <some directo ry inr
RE: /#cvs.lock): No such file or directoryctory for <some directo ry inrepository>
Wed, 18 Aug 2004 17:28:28 -0400
Jim Page wrote:
> What you are suggesting, and is also suggested in the above
> postings, is
> having 2 sandboxes, 1 linux and 1 windows, right?
Are any of your developers working simultaneously on Windows and on Linux?
If not, then only one working directory is needed.
Why do people call these "sandboxes"? I'm a professional software developer,
not a kid playing in the sand.
> As a common sense
> approach to version
> control, I try to get my people to a) not commit anything
> unless they are
> pretty sure it builds and works, b) put meaningful comments
> in the logs.
Good strategy, within reason. It really depends how you define "works",
though. If you mean "no bugs at all", then I disagree. If you mean "no bugs
that will significantly affect others" then I'd agree.
I prefer the guideline "don't break the build" - i.e. make sure it builds.
Frequent commits (by which I mean no more than a day or two apart) and
frequent updates make merging much easier.
> Getting this surely very common scenario to work reliably
> with a shared
> directory would certainly go on my wish list.
Unfortunately, this is outside of CVS's control. CVS is at the mercy of the
underlying operating system here. You'll have to talk to the
Samba/NFS/whatever implementors to get that fixed up.
Senior Software Designer
Leitch Technology International Inc. (http://www.leitch.com)
Columnist, C/C++ Users Journal (http://www.cuj.com/experts)
- RE: /#cvs.lock): No such file or directoryctory for <some directo ry inrepository>,