You could try fossil bundle export/import. I think there is an option there to ignore project id when importing. I used this to import branches, it should work with trunk as well. I am not sure if this brings tickets across. -- Original Message From: Zoltán Kócsi Sent: Friday, 17 July 2015 09:27 To: Fossil SCM user's discussion Reply To: Fossil SCM user's discussion Subject: [fossil-users] Merging repositories
A question about merging projects: Given two repositories hosting project A and project B, we want to merge merge them into a project C. Basically they go into a common source tree and become sub-projects of the new C project. One solution is to just build the new source tree and start a new repository C. However, that way we lose all the history of both A and B, not to mention all the ticket databases. My question is, is it possible to move artefacts from one Fossil database to an other? I've read through the technical documentation of Fossil and it seems to me that there's nothing to stop one from doing so, but I am not sure whether I've missed some subtle but fundamental barrier, hence the question. Also, if it is possible at all, and I am not the first one to have this problem, is there a tool already made that does what I want or should I start hacking a Tcl script together that gets the entries from the two databases and puts them together in a third one, with all the changes of the references in the file artefacts and so on? Thanks, Zoltan _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
