Dear Laine Stump,
> Oddly, http://www.wincvs.org points people at this mailing list (the CVS
> mailing list) when they have questions about WinCVS. I'm not sure why
> they haven't setup their own mailing list, as other frontends, such as
> tkCVS, have. It would seem to make *a lot* of sense to do so...
>From the WinCvs webpage you can read:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
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....
2. Webpage clearly states to report the bugs on the WinCvs's own bug
tracking system. IT IS SETUP!
3. Comments and suggestion DOES not point to the cvs mailing list.
So what is your problem here?
And, honestly, the reported problem was about locking, which is the CVS
problem, not WinCvs.
BR,
Jerzy
The first thing they don't teach you at school: "Never say never".
All the issues not related to the list please send to me in private, thanks.
----- Original Message -----
From: "Laine Stump" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 12, 2000 3:35 AM
Subject: WinCVS and the info-cvs mailing list
> Larry Jones writes:
> > CVS, which is what this mailing list
> > focuses on, is a command-line utility
> > [...]
> > WinCVS is a completely separate (though related)
> > product.
>
>
>
