[cvsnt] Re: WinCVS or TortoiseCVS?
Chuck.Kirschman at bentley.com
Fri Jul 23 21:45:21 BST 2004
Almost all programmers here prefer the command line interface.
Non-developers like the gui apps. Doc likes winCVS, VB people like
Tortoise. The people that build the web pages insist on something that
works from within Visual Studio or they will use SourceSafe, so we
hooked them up with one of the available plug-ins. Since there's no
issue with swapping between them, just let each person pick their own.
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Terence Wilson
Sent: Friday, July 23, 2004 3:25 PM
To: cvsnt at cvsnt.org
Subject: RE: [cvsnt] Re: WinCVS or TortoiseCVS?
Around here the preference is most definitely TortoiseCVS over WinCVS,
several of the programmers in my group used profanity when describing
their WinCVS experience, but I'm sure it must have some virtue.
Personally speaking I think there's no contest.. TortoiseCVS rocks.
> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Glen Starrett
> Sent: Friday, July 23, 2004 9:35 AM
> To: cvsnt at cvsnt.org
> Subject: [cvsnt] Re: WinCVS or TortoiseCVS?
> Paul Nusbaum wrote:
> > Otherwise I'm mostly unfamiliar with these tools - and was curious
> > what your tool of choice is for client machines, and why?
> I use TortoiseCVS, since it's most familiar with the way that
> I use CVS.
> WinCVS has some nice features (e.g. showing missing files,
> macro support, flat view, filters, ...) but I'm more
> comfortable with using CMD + TortoiseCVS for my needs. I
> like the convenience of having TortoiseCVS integrated in the
> shell. I suppose if I used a lot of large sandboxes then I
> might want to use something more sophisticated.
> Glen Starrett
> cvsnt mailing list
> cvsnt at cvsnt.org
cvsnt mailing list
cvsnt at cvsnt.org
More information about the cvsnt