Sorry for stalling this discussion a bit. I think we reached a
conclusion of sorts, here's my proposed plan in detail:
- We use nested repositories. This is forward compatible
with the various schemes for better handling of nested
repos in the future that were raised on the Darcs list.
- We create the following darcs repositories:
ghc
containing the files in fptools, plus
these subdirectories (only):
distrib, docs, ghc, glafp-utils, mk
libraries
from fptools/libraries
nofib
from fptools/nofib
testsuite
from fptools/testsuite
- synchronisation: we go with David's suggestion of starting
with CVS->darcs syncing, so that we can test working with
the darcs repo and letting people pull it, and then switch
the direction of the sync later.
- branches: these are quite tricky. I'm only interested in
the ghc-6-4-branch right now, and this doesn't need to
sync with HEAD, but it would be nice if it had
a common history up to the branch point. We can leave
the other branches for now.
John, are you happy to go and set this up? Anything else you need?
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-ghc
