On May 15, 2017, at 8:21 AM, Roy Keene <fos...@rkeene.org> wrote: > > what you are probably doing now is creating a new repo with the same project > code then pushing to that, which won't work out great.
To clarify, one of the things Fossil does when it creates a new repository is to generate a universally unique project code, which was done on both sides — once for your local repo and once for the remote chiselapp.com repo — so the two repos are essentially incompatible. No matter which direction you push, the receiving repo will decide those artifacts aren’t for it, so it will ignore them. It would defeat some Fossil’s core security architecture to allow a “foreign” repo to push the way you tried from start. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
