Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
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 cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > 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 downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs >