On Sat, May 31, 2014 at 1:21 PM, Richard Hipp <d...@sqlite.org> wrote:
> 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? > It doesn't solve a problem so much as open up a minor new feature (the ability to have all commit messages in one's preferred language). i would personally like to see it kept (mainly for future compatibility with libfossil, which doesn't require an initial checkin ;), but not as the default. The default should stay as it historically has been - creating the hard-coded empty commit. Once i'm back from shopping i'll work on a patch which reverts to the previous default behaviour and adds a new flag for those who want to create/play with an empty repo (which still likely has open corner cases involving RID 0). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
