On Thu, 10 Feb 2011 21:41:24 -0200 Marcos Gambeta <marcos.gamb...@yahoo.com.br> wrote:
> Em 10/02/2011 19:30, Andi Jahja escreveu: > > Hello, > > > > It seems that CVS resumes to work. > > Opinions? > > > > Andi > > > > > > Andi, > > Another idea: > > . enable subversion repository in the 'xharbour' project (see features > in the admin area) > > . commit the current code that are in the 'xhrb' project into the new > 'xharbour' repository > > . developers continue using 'xharbour' and the subversion repository > > . cvs repository remain for reference > > . 'xhrb' is closed This means "renaming" xhrb to xharbour, is it not? As I said in my previous mail, I was not able to create xharbour. I guess the reason is that there is alreary 'xharbour' in CVS (although CVS and SVN are not related each other, CMIIW). Perhaps, we can create xharbour in SVN by migrating via CVS2SVN.. but sorry I do not know how :-( I you can help us on this, it will be greatly appreciated. > Sorry if I'm being insistent on this idea, but I'm wondering what would > be best for admins, developers and users. :-) Nothing to sorry about. I am glad you contribute ideas for xHarbour existence. Andi ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ xHarbour-developers mailing list xHarbour-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xharbour-developers
