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 firstname.lastname@example.org.
Actually, I am thinking that recently in the CVSNT 126.96.36.199 source there are quite a few bug fixes (for example, didn't "cvs edit" get fixed?). These bug fixes are important to (some) TortoiseCVS users. However, there are also a lot of non-bug-fix changes in the CVS 188.8.131.52 source that may cause a lot of instability. In addition, at least one TortoiseCVS user complained about the lack of rsh support, so I'm thinking to add that if it isn't a pain in the ass. So, I am thinking to create a branch that will merge _only_ the bug-fix changes from CVS 184.108.40.206 into CVS 220.127.116.11 so that TortoiseCVS can ship a up-to-date (bugfix-wise) CVSNT while the new features of 18.104.22.168 are in development. Does that sound reasonable? - Brian Brian Smith wrote: > I thought people on the list might like to know that as of TortoiseCVS > 0.48, CVSNT 22.214.171.124 is the default cvs implementation. Previously, they > were shipping the regular CVS 126.96.36.199p1 client, I believe. > > I didn't have anything to do with this change other than suggesting it. > > - Brian > > > > > _______________________________________________ > Cvsnt mailing list > Cvsnt at cvsnt.org > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs