On 8/8/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
> 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.
Yes. I was thinking exactly that yesterday. But we don't need to have
a CVS copy at all IMO. We can just dump a ChangeLog and keep that for
reference. The CVS repo will still be available from the old libxml
site. So we can go ahead a start with a fresh copy.
Does any one want to do the import, or should I? I'm thinking of this layout:
branches/
tags/
0.3.8.4/
trunk/
Where trunk contains Ross' 0.4.0pre01 version. Does that work for everyone?
> 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?
There's the new mailing list ([EMAIL PROTECTED]), but do
you mean IRC or a Wiki or?
T.
_______________________________________________
libxml-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/libxml-devel
