On Wed, Jul 12, 2000 at 11:24:38AM +0800, Win32 M$ wrote:
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> WinCvs support
> Subscribe to the cvs mailing list.
> Report/Track bugs using the Bugzilla bugs system.
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> And then at the bottom you can read:
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> That's all folks If you have comments or suggestions, email me at
> [EMAIL PROTECTED]
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> So:
> 1. It says "subscribe", it doesn't say "post the questions about WinCvs
> there". I guess the idea is to let the people to 'read' some posts to learn
> about the CVS etc. Also, most of the question about WinCvs actually IS a
> questions about CVS. The problem with locking IS A CVS PROBLEM, we wouldn't
> have to change a single line of WinCvs/MacCvs code to make locking working
> properly, the CVS itself screwed it up and it should be fixed this way or
> another IN THE CVS. For example, the guy would have to apply patch to his
> SERVER CVS (perhaps UNIX and command line), not to the WinCvs....
Come on, read again what you have written above!
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> WinCvs support
> Subscribe to the cvs mailing list.
? Please admit, that one could get the opinion that the cvs mailing list
is the list for WinCVS support. At least I did, as I read the page.
> 2. Webpage clearly states to report the bugs on the WinCvs's own bug
> tracking system. IT IS SETUP!
As long as users do not want to submit bug reports and really help
improving a system they send their mails to lists hoping that someone
immediately replies with a patch and/or a problem solution.
> 3. Comments and suggestion DOES not point to the cvs mailing list.
Hm, I am on the web for several years now and in most cases, those
bottom addresses are associated with the web master ... ;).
> So what is your problem here?
No problem.
> And, honestly, the reported problem was about locking, which is the CVS
> problem, not WinCvs.
? Please provide where the problem in commandline CVS is? If I remember
correctly, I took the same steps as the original poster (who did it with
WinCVS) and got no problems.
Regards,
Matthias
--
Matthias Kranz [EMAIL PROTECTED]
http://www.belug.org/~kranz
"Ever tried. Ever failed. No matter. Try again.
Fail again. Fail better." (Samuel Beckett)
