I'd virtually guarantee that 20 students - and only the ones running using the apt-get fossil - did not try the --empty switch.
Unfortunately. And when I added tags to the empty timeline they were still not mergable. ../Dave On 11 March 2015 at 15:10, Andy Bradford <amb-fos...@bradfords.org> wrote: > Thus said Richard Hipp on Wed, 11 Mar 2015 12:48:04 -0400: > >> I'm still curious as to how the students managed to get the repo into >> this state, too. > > This is possible if you open a repository using the --empty command line > option. Basically, what you end up with when you do this are two DAGs in > the repository, each with their own independent line of development. > This means that merging between the two won't really be possible, (or > perhaps very difficult) because they are not at all related in their > DAG. > > Did the students use --empty (perhaps misunderstanding what it is used > for)? > > Andy > -- > TAI64 timestamp: 4000000055009345 > _______________________________________________ > 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
