Am 13.03.2015 um 10:59 schrieb Jan Nijtmans:
If the initial commit contains files, Fossil 1.27 doesn't see that, and nothing
reveals they are really there. Therefore, those files look as they have been
lost, but they really aren't: just upgrade to Fossil 1.28 or later and the files
will magically be back again.
Thats right. Switching to a newer Fossil the timeline still is split but
all files (from both lines) are accessible in the reposiory.
Nonetheless: I'm lost on how to join the lines again -- no chance
without a common ancestor. Seems to be a repository containing two
separate repositories.
A tricky SQL statement could probably create the required records...
Thanks to Tontyna for his excellent analysis, which made it
(at least to me) fully clear what really happend here.
My pleasure. BTW it's "her" not "his" ;)
Regards,
Tontyna
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
