On Wed, Apr 16, 2014 at 11:35 AM, Joerg Sonnenberger <[email protected]> wrote: > It would also be nice if clone didn't abort with removal of the > repository on such errors. pull/push should return an error etc. > There are a bunch of basic usability issues in this area. This is made > worse by pull not being read-only...
It would be even nicer if it didn't throw away partial "pull" data on a DB timeout: I'm trying to pull the latest NetBSD changes (to pull in the Heartbleed fixes) and my session keeps failing with the "fudge time" error. Unfortunately, this means all the data it transferred (sometimes over 1GB!) gets rolled back and I have to try again later. 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. -- Rich _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
