On Sun, Dec 27, 2015 at 10:23 PM, Richard Hipp <[email protected]> wrote: > Still working on the ability to clone a Git repository - that feature > is not ready yet.
I've seen your documentation changes with regarding to hierarchical manifests. Great think you specify first. > However, one side effect of the Git clone effort is that the > fast-import logic of Fossil has been improved. It should run faster > now, and use a lot less disk space. Can you please try your import > again and let us know what happens? I've seen your HEAD changes, I'm on 2dd25909da and the space-effeciency is really nice to have. I'm not sure if this is faster than in the past since I'm not testing on the same hardware setup. I'll see if it crashes or not and if not, then I'll fire on the original test server and test there. Anyway, this is just a test to see how fossil behaves with this size of repository. My final goal would be to have OpenBSD CVS mirrored into fossil. It's a question if to use cvs->git->fossil transition here especially when considering incremental imports or just write some tool to do proper cvs->fossil import. I see you tune for speedy git import and I can understand motivation behind this direction but if you do have some idea how to proceed in cvs import case, then it would be appreciated here. Thanks! I'll keep you posted about the testing results of course... _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
