Re: Current CVS Repository Location

2005-08-24 Thread David Sugar
ednesday, August 24, 2005 17:48 To: Conrad T. Pino Cc: Bug Common C++ Subject: Re: Current CVS Repository Location Currently we are using the sourceforge one. This was because I could consolidate all my work and all the packages where I am the primary or only person currently doing active change

RE: Current CVS Repository Location

2005-08-24 Thread Conrad T. Pino
ay, August 24, 2005 17:48 > To: Conrad T. Pino > Cc: Bug Common C++ > Subject: Re: Current CVS Repository Location > > Currently we are using the sourceforge one. This was because I could > consolidate all my work and all the packages where I am the primary or > only pers

Re: Current CVS Repository Location

2005-08-24 Thread David Sugar
Currently we are using the sourceforge one. This was because I could consolidate all my work and all the packages where I am the primary or only person currently doing active changes in just one place under one repository. The one exception is ccrtp, which is also very activily maintained by

RE: Current CVS Repository Location

2005-08-24 Thread Conrad T. Pino
PROTECTED] Behalf Of > Conrad T. Pino > Sent: Wednesday, August 24, 2005 14:34 > To: Bug Common C++ > Subject: Current CVS Repository Location > > Hi David, > > I've located at least three CVS archives for the Common C++ project: > > http://cvs.sourceforge.ne

Current CVS Repository Location

2005-08-24 Thread Conrad T. Pino
Hi David, I've located at least three CVS archives for the Common C++ project: http://cvs.sourceforge.net/viewcvs.py/gnutelephony/testing/commoncpp2/ http://cvs.sourceforge.net/viewcvs.py/cplusplus/commoncpp2/ http://savannah.gnu.org/cgi-bin/viewcvs/commoncpp/commoncpp2/ which were respectively