On Nov 3, 2014, at 7:01 PM, E. Timothy Uy <t...@loqu8.com> wrote: > Is that a philosophical question? :)
No, it’s a persuasion challenge. I’ll propose it in two parts: 1. Why is it a good idea for you, E. Timothy Uy, to dump the SQLite code repo into a Git repo? What does this achieve, that keeping it in Fossil does not? 2. Why is it a good idea for our BDFL, D. Richard Hipp, to modify the SQLite repo to make it easier for you to dump it into a Git repo? Keep in mind that the costs here are not just his time, but also the loss of a test case. I don’t think you can convince anyone that #2 is a good idea, but I’m curious about why #1 is a good idea. Bonus persuasion point 3: Why not persuade the Git people to modify their tool to cope with time warps? Isn’t their major value proposition w.r.t the other open source DVCSes that Git is more powerful and flexible? Here we see Fossil doing something Git cannot or will not do, and it’s not a matter of mission scope, as with the bug tracker or wiki features of Fossil. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
