Luis: The command was written in my messages :) It is:
svn co https://xharbour.svn.sourceforge.net/svnroot/xharbour/trunk/xharbour xharbour Andi On Sat, 12 Feb 2011 21:04:31 -0800 Luis Krause Mantilla <lkrau...@shaw.ca> wrote: > Andi: > > When I do this new checkout, it creates xharbour\trunk\xharbour > How can I make it just save to xharbour like with the initial > SVN setup you did (or like we did with CVS)? > > Regards, > > On 11-02-2011 04:39, Andi Jahja wrote: > > On Fri, 11 Feb 2011 08:46:55 +0100 > > "Patrick Mast, xHarbour."<patrick.m...@xharbour.com> wrote: > > > >> Hey Andi, > >> > >>> Oh, OK I've found the features. Will commit the files there now and > >>> close xhrb. > >> > >> So we will have SVN "xHarbour" instead of "xhrb"? > >> > >> The mailing list works OK for me, why should we move it to a Google? > >> Any advantages we don't have now? > > > > Patrick, > > > > "xhrb" has been flagged for removal. > > The new repository now is: > > > > https://xharbour.svn.sourceforge.net/svnroot/xharbour > > > > To do a check-out: > > > > svn co https://xharbour.svn.sourceforge.net/svnroot/xharbour/trunk/xharbour > > xharbour ------------------------------------------------------------------------------ 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
