Quite frankly, the simplest way is to probably to export a fossil repository to git, use the git function as known, and then reimport into a new fossil repository. I also think this was discussed a few months ago, but I can't seem to find the emails from that.
Tomek On Tue, Mar 6, 2012 at 10:19 AM, Bill Burdick <[email protected]>wrote: > Sounds pretty useful. A start might be to write a script that uses fossil > deconstruct and produces a new directory of artifacts by filtering each > commit, calculating IDs for the new commits, and copying the referenced > artifacts to the new directory, then uses fossil reconstruct to build the > new repository. > > Sounds like a neat project, and pretty doable. > > > Bill > > On Tue, Mar 6, 2012 at 4:05 AM, Gérald <[email protected]> wrote: > >> Hello, >> >> Assume my repository has the following structure: >> >> /Project >> /Project/SubProject-0 >> /Project/SubProject-1 >> /Project/SubProject-2 >> >> and the repository has quite some commits. Now one of the subprojects >> (SubProject-0) grows pretty big, and I want to take SubProject-0 out >> and set it up as a standalone project. Is it possible to extract all >> the commit history involving SubProject-0 from the parent fossil >> repository and move it to a new one? >> >> Thank you >> _______________________________________________ >> fossil-users mailing list >> [email protected] >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
