[EMAIL PROTECTED] on 02/12/2000 05:09:09 PM >Maintenance - sure it needs locking. In the case when you have to freeze >code to get it to the proper condition or synchronize (migration) with other >tools - how do you stop commiting? You can tell everyone not to commit. You can lock the filesystem (hopefully you have your repository on a separate filesystem). You can manually create lock files within the modules (I have a rudimentary script if you want it). > And, you don't want to take the repo >offline, because it hurts the development. I think "cvs -n" ignores locks. So, if you're using the module-locking script, those who wish to continue development can use "cvs -n command". Noel
- Re: CVS File Locking John Macdonald
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking John Macdonald
- Re: CVS File Locking Tobias Weingartner
- RE: CVS File Locking Paul Sander
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Noel L Yap
- RE: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Noel L Yap
- Re: CVS File Locking Paul Sander
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Frode Nilsen
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Frode Nilsen
- Re: CVS File Locking Kate Ebneter
- Re: CVS File Locking Frode Nilsen
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Frode Nilsen
