On Fri, Jun 21, 2013 at 1:35 PM, B Harder <brad.har...@gmail.com> wrote:
> I realize this check is early in the commit phase, but now I wonder: > barring pushed/autosync'd content, can one "pop" or unwind the last commit > of a local repo? > > > An "uncommit" command has been on the to-do list for a long time, but has not yet been implemented. 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. When you want to undo a check-in in Fossil, the typical procedure is to move that check-in off into a dead-end branch named "error" or "mistake". Example here: http://www.fossil-scm.org/fossil/timeline?n=8&c=2011-06-16+18:10:54&y=ci VCSes that have an uncommit command allows one to "airbrush out" embarrassing missteps. Fossil, on the other hand, forces us to own up to our errors. "Fossil: Encouraging confession, penitence, and humility since 2007" ;-) -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
