If it is possible to have both CVS and SVN under the project, then one option is to get a full historical copy of the libxml CVS repo and put it into libxml2 and just leave it for reference. Then import the latest into SVN and just start from there. As long as the logs are accessible, it matters less if they are in the same repo.
I have made some contributions to libxml (am a C programmer) and have done this very fork thing before when I started bdb2 on rubyforge. Is there some way that the C programmers can coordinate so we can all understand the problems and we can unify a strategy for dealing with them? Dan On Aug 6, 2007, at 16:29, TRANS wrote: > On 8/6/07, Ross Bamford <[EMAIL PROTECTED]> wrote: > >> I'd say there's too much good code in there to just throw it away >> - a lot >> of the current code works well, and is tested to at least some >> extent. >> Plus, there seem to be a lot of patches floating around again. >> >> In terms of moving forward, IMO it'd be worth making reference to >> ruby-xml-smart, which does some of what we do, without the bugs... >> http://raa.ruby-lang.org/project/ruby-xml-smart/ > > Cool, looks like they made some progress since I last looked at it. > Yes, that's good to know about --its not a full binding, not intended > to be, but could still be a good resource. > >> cvs2svn would be great, but I think it's best to have filesystem >> access to >> the repository. I'm pretty sure it's running on rubyforge already >> though, >> since I've converted other projects from CVS without (IIRC) losing >> the >> history, but I think you'd have to ask Tom to run it cross-project... > > Oh, cool. I'll ask Tom if he can do that. If he can, we should be all > set. If not, well we can just start with a fresh repo. I don't think > it matters too too much. > > T. > _______________________________________________ > libxml-devel mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/libxml-devel _______________________________________________ libxml-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/libxml-devel
