On Wed, Apr 16, 2014 at 10:40 PM, Rich Neswold <[email protected]>wrote:
> It would be nice if fossil would break the "pull" into smaller > transactions which contain valid timeline commits so, if there's a > database timeout, the next time I try to "pull" it can continue where > it left off. > That's a very interesting idea. That's not something for a weekend hack (it would require bigger changes), but that would certainly be of benefit in libfossil once it is far enough along to sync. There's no specific reason why it has to internally track the transient sync data the same way fossil(1) does. e.g. it might make sense to buffer it all to an extra table and then feed that table to the part which does the real work. -- ----- 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 [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
