On Oct 2, 2014 11:14 AM, "Andy Bradford" <amb-fos...@bradfords.org> wrote: > > Thus said Stephan Beal on Thu, 02 Oct 2014 19:31:12 +0200: > > > The weird thing is, he's got two "initial empty commits". i'm at a > > loss to explain that. > > Seems that one of them must have been created with an older fossil and > the other created with a newer version from Fossil's trunk which > currently does not force an initial commit comment of ``initial empty > check-in'' when the fossil is created.
Is that even possible? I thought the repo would have to be created once (and only once), generating it's repo-id, and then cloned for all subsequent copies before things can begin deviating. > Would be interesting to know how the repository was created. I don't > know how Chiselapp imports a repository, but is it possible that the it > might have created the additional trunk when it was uploaded? > > Andy > -- > TAI64 timestamp: 40000000542d9630 > _______________________________________________ > 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
