On Fri, Jun 21, 2013 at 8:01 PM, Richard Hipp <d...@sqlite.org> wrote:
> An "uncommit" command has been on the to-do list for a long time, but has > not yet been implemented. > And i've only missed it once or twice - i know this is a corner case and impossible when syncing is on. > Note that "uncommit" is considerably less useful in Fossil compared to > Git, since Fossil normally has autosync turned on so that your content gets > pushed automatically right after the commit in most cases. And everybody > agrees that uncommit is not feasible once you have pushed. > i had, incidentally, turned off autosync by accident because i thought that two 'opens' of the same repo did not share that setting (i have a test copy which i don't want to autosync, but i just realized 4 minutes ago that they share that setting). So in this once in a million case i could have used an uncommit, but autosync is normally always on. So IMO it's not worth the implementation hassle (it wouldn't/couldn't help me very often, in any case). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
