The repository provided to the students *did* have commits: .fossil-settings with 4+ files and 6 directories with .hold files in them. But maybe what you're saying is that something post-1.27 to support that caused other problems.
../Dave On 12 March 2015 at 10:34, Richard Hipp <d...@sqlite.org> wrote: > On 3/12/15, Jan Nijtmans <jan.nijtm...@gmail.com> wrote: >> >> Much better, preventing the problem all together: create the >> repository with Fossil 1.27 to begin with. Fossil <1.30 had >> bugs which ill-treat repositories without any commits. Those >> were fixed in Fossil 1.30. >> > > Just to be clear: Those changes that allow one to create a repo that > has no commits - they are going to be backed out just as soon as I get > the opportunity. > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > 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
