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.
When I tried that, all of the history was lost, as well as some of the required info in the modules folder. The "missing" files (when we try to compile) are actually files in the Attic folders. When we checkout the files, we do not get the files in the Attic folders. How can I get them as part of a checkout? Thx for everyone's help so far. "Gabriel Genellina" <gagsl-cvsnt at yahoo.com.ar> wrote in message news:mailman.550.1169504652.16616.cvsnt at cvsnt.org... > At Monday 22/1/2007 13:43, Tim Chippington Derrick wrote: > >>Just a thought... I haven't done a CVS migration from GNU CVS to >>CVSNT, or from Unix/Linux to Windows, but even moving my repository >>from an existing Windows+CVSNT to a new Windows+CVSNT box I would >>always use CVSNT to create the repository first and then copy the >>repository contents into the (newly created and initialised) >>repository. I've done this many times and never had a problem; I >>don't know what extra stuff CVSNT does or needs in the repository >>beyond what GNU CVS does, but can imagine that not having a correctly >>initialised CVSNT repository as a starting point could be a problem. > > I was going to say exactly that. > Looks a lot safer to let CVSNT initialise the repository first, then > update then CVSROOT config files, and then copy all the repository > previous contents (*excluding* the CVSROOT directory). > > > -- > Gabriel Genellina > Softlab SRL > > > > > > __________________________________________________ Preguntá. Respondé. > Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en > Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas