On Tuesday, February 15, "Win32 M$" wrote: > > I probably will soon or later, but I want to know the opinions of the CVS > experts about the problem. I got few valuable pointer (thanks Paul and Noel > and others) and few less valuable (thanks Greg:). I think it is good to make > some discussion as topic seems quite important. I would like to know the > official CVS developers opinion, but I only see silence. If I code the > stuff, and it is never going to happen - why bother? Well, in some sense of the word you have just discovered free software development. You don't get paid for it, you don't get guarrantees that it will be accepted. --Toby.
- Re: CVS File Locking Tobias Weingartner
- Re: CVS File Locking Win32 M$
- Re: CVS File Locking Win32 M$
- Re: CVS File Locking Tobias Weingartner
- RE: CVS File Locking Win32 M$
- Re: CVS File Locking Win32 M$
- 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
- Re: CVS File Locking 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
