Greg A. Woods" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> [ On Monday, April 29, 2002 at 15:48:37 (-0500), Gilroy, Michael -AES
wrote: ]
> > Subject: File Locking with CVS
> >
> > My manager won't let me use CVS with concurrent versions o
[ On Monday, April 29, 2002 at 15:48:37 (-0500), Gilroy, Michael -AES wrote: ]
> Subject: File Locking with CVS
>
> My manager won't let me use CVS with concurrent versions of files. I need
> to have the file locked when I edit the file (cvs edit) so that no one else
> can d
--- [EMAIL PROTECTED] wrote:
> You could write a perl script that would take a file
> name and do
> a "cvs editors" on it. If there were any, it could
> list who is
> editing the file and end, and if there were none it
> could do a
> "cvs edit".
There's a race condition here in which there's a
> My manager won't let me use CVS with concurrent versions of files.
That means CVS is not really suited for your needs. If you are doing
normal software development, you will find that concurrency works,
regardless of what your manager says. It will solve many more problems
than it creates.
--- "Gilroy, Michael -AES" <[EMAIL PROTECTED]>
wrote:
> My manager won't let me use CVS with concurrent
> versions of files. I need
> to have the file locked when I edit the file (cvs
> edit) so that no one else
> can do a 'cvs edit' until I either do a 'cvs unedit'
> or a 'cvs commit'.
> This wo
My manager won't let me use CVS with concurrent versions of files. I need
to have the file locked when I edit the file (cvs edit) so that no one else
can do a 'cvs edit' until I either do a 'cvs unedit' or a 'cvs commit'.
This would be similar to the way SCCS and RCS work. However, I also need
s
