2014-10-02 20:54 GMT+02:00 Andy Bradford:
> The project-id is stored in a table in a database---it can be changed. I
> suspect that this is how Chiselapp actually allows you to sync a new
> repository to their site in some configurations. Because the act of
> creating a new repository necessarily also includes an initial commit
> (older versions of Fossil), you end up with two trunks because there
> were actually 2 repositories created, not one. The ability to create a
> repository without an initial commit might be something that Chiselapp
> could take advantage of in this case.
Nice explanation! Thanks!
2014-10-02 21:02 GMT+02:00 dave <d...@ziggurat29.com>:
> Now the question is whether that behaviour of creating
> two disjoint trees in one repo upon project id change is a bug.
Yes, this sounds like a bug in chiselapp (not in fossil!). Normally,
synchronising two separate repositories (which each have their
own initial empty checkin) is not possible because
they have a different project-id. But if chiselapp allows to change
the project-id, then the two different initial check-ins will
be moved over to both sides of the sync. "fossil new --empty"
would indeed help chiselapp here (which is already available in
fossil 1.29), preventing the two initial checkins in this situation.
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
