On Thu, May 12, 2011 at 3:26 PM, Ron Aaron <[email protected]> wrote: > > > What version of Fossil was able to rebuild this repo? Can you bisect and > figure out when it broke? > > > I haven't looked at what broke, but for the first time I used the 'bisect' > command -- and wow, what a great tool! > > Here is the output: > > 14253e9b3336a6292432 2010-01-09 18:32:28 BAD > 6069602aba14bf74b8f4 2010-01-09 13:11:18 GOOD CURRENT >
Thanks for bisecting. However, this doesn't really give any new clues. The only code changes between 6069602aba14bf74b8f4 and 14253e9b3336a6292432 are in the "/reportlist" web page (which gives a list of available ticket reports) and have absolutely nothing whatsoever to do with the "rebuild" command. :-\ > > So this particular problem has been around almost a year and a half; I > guess I have a particularly weird repo. > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
