[EMAIL PROTECTED] on 02/15/2000 12:27:33 PM >Don't you worry - I remember about "cvs edic -c" path. I think that at the >moment we are talking about what to do with the current "cvs admin -l". I am >that close to say to remove it completely, however I like the idea of having >it under control better. I believe that completely removing it will do no >good... Since I don't use "cvs admin -l", it doesn't matter much to me what happens to it. However, removing it is on the slate (someone else has brought it up). This should be a warning for those still using to learn of other ways and migrate their team processes. Noel
- Re: CVS File Locking Win32 M$
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Win32 M$
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Win32 M$
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Paul Sander
- RE: CVS File Locking Chris Cameron
- Re: CVS File Locking Noel L Yap
- cvs history command? Noel L Yap
- cvs history command? |}avid (opeland
- Re: cvs history command? Greg W. Moore
- Re: cvs history command? |}avid (opeland
- Re: cvs history command? Greg W. Moore
- Re: cvs history command? Larry Jones
- Re: CVS File Locking Win32 M$
- Re: CVS File Locking Paul Sander
- Re: CVS File Locking Greg A. Woods
- Re: CVS File Locking Paul Sander
- Re: CVS File Locking Greg A. Woods
