The real bottleneck is usually the CVS protocol itself and that will behave the same regardless of which GUI frontend you use.Īlso, what exactly do you mean by "has no merge dialog"? So, I'd be interested to hear what particular operations you think are slow in WinCvs. They're all "just" GUI frontends on top of the CVSNT commandline client (IIRC only SmartCvs uses a plain CVS client). First: Strictly speaking, none of the tools quoted here so far are CVS clients.
0 Comments
Leave a Reply. |