Dennis wrote in news: snipped-for-privacy@clarityconnect.com:
Or running in "ntserver" mode using the very nice NT-native CVS service cvsnt. If you don't have a *nix box, use cvsnt and have all your Windows boxes connect securely via cvsnt. WinCVS supports the "ntserver" mode as well. See:
This might be true for Windows 95, 98 or Me but if you are running Windows NT, 2000 or XP (with full service packs applied) then stability is not quite as bad as it used to be :)
If you want to give CVS a test run in local (or client server) mode you might want to take a look at the Zeus editor:
Zeus has has fully integrated integrate CVS support.
Jussi Jumppanen Author of: Zeus for Windows (All new version 3.90 out now) "The C/C++, Cobol, Java, HTML, Python, PHP, Perl programmer's editor" Home Page:
Ken
We've just had Merant in to demo PVCS. You don't seem to be able to branch at a project level. Is that right? We were told that PVCS could only branch on a file by file basis. Is that correct?
Cheers TW
As do many other editors.
-- Al Balmer Balmer Consulting snipped-for-privacy@att.net
You can run CVS against a file residing on your server. I have at least not seen any problem with this.
BTW for a wery nice client take a look at:
/RogerL
I haven't needed to branch at the project level, but you're probably right. Basically we manage product variants by using file branching & judicious labelling. I'm not an advocate of branching & would recommend that for an extensive product variant, a complete copy of the project would be preferable.
Ken.
+====================================+ I hate junk email. Please direct any genuine email to: kenlee at hotpop.comHave something to add? Share your thoughts — no account required.
Ask the community — no account required