With a post that someone made here, and the thought that I've been running in my head over the past while...
How does one have their own code base for SQLite, with their own customer logic or functionality or whatever, then, have updates provided by the SQLite team implemented in when updates and such are provided? I'm assuming Fossil would handle this kind of process with merging and such? What is the workflow on making sure the amalgamation source doesn't modify local changes? _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
