On Fri, May 30, 2014 at 8:14 PM, Andy Bradford <amb-fos...@bradfords.org> wrote:
> Looks like this is due to the recent addition of the empty initial > checkin in [cac91b6cd17ab746]: > Can somebody please explain to me what this change accomplishes, other that introduce needless bugs, which it seems to excel at? What problem does it solve? Why shouldn't we back it out? > > $ fossil bisect bad > bisect complete > 2 BAD 2014-05-30 18:12:29 52d242a73be2d7d6 > 3 BAD 2014-05-24 06:27:01 a74d100a121219b8 > 4 BAD 2014-05-22 04:39:11 941ead2f9ad6f9ca > 5 BAD 2014-05-19 09:56:31 c543079b87ce4b6c > 6 BAD 2014-05-19 09:16:20 c060947196baef2d > 7 BAD 2014-05-19 07:38:04 cac91b6cd17ab746 > 8 CURRENT 2014-05-19 07:38:04 cac91b6cd17ab746 > 1 GOOD 2014-05-14 16:05:34 ec44f61a831e4225 > > It's easy enough to reproduce. Create a new empty repository. Add 2 > files but only try to checkin 1 of them. > > Andy > -- > TAI64 timestamp: 4000000053891f13 > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- 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
