Of course I can parse the timeline, get all revisions for a branch, manually update the working directory to each of them and then commit them to a new empty repository, but that's a lot of additional work. Maybe fossil can do this on its own?
I know this sounds like an XY problem but I see no reason why doing this would be a bad idea: the original repo has only code - no wiki docs, no tickets, so extracting a branch to another repo won't lose anything I assume. Also, the original repo will remain intact so I'm not deleting any history. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
