On Mar 6, 2010, at 6:29 AM, Twylite wrote:
> Hi,
>
> Is it possible to merge two repositories, or to import one repository
> into another?
Suppose your two projects are A and B. You want to import B into A.
First find the "project-code" for A using the "fossil info" command.
Then change the project code of B to match the project code of A using
the sqlite3 command-line client:
sqlite3 B.fossil "UPDATE config SET value='project-code-for-A'
WHERE name='project-code';"
Then you will be able to "push" all the content of B into A.
>
> I would like to retain the identity of one repository (and if possible
> its artifact IDs), but I don't really care about the artifact IDs of
> the
> repository being imported -- mainly I want to bring all history of two
> different projects into one repository.
>
> I seem to have managed something along these lines by deconstructing
> multiple repos into one folder, and then reconstructing a new
> repository
> from that folder.
>
> One problem I have encountered is that the new repository is just
> that:
> new. It has a different project-id and server-id. This seems to be a
> feature of reconstruct even when a single repo is involved. The
> effect
> is that I get C = A + B, rather than A += B, which means that existing
> clients of my large repository A will need to clone a new repository
> (in
> this case C) if & when I do such merges, rather than just pulling down
> updates.
>
> Any suggestions?
>
> Regards,
> Twylite
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
D. Richard Hipp
d...@hwaci.com
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
