On Jul 6, 2017, at 8:38 AM, Natacha Porté <nata...@instinctive.eu> wrote: > > I was recently in a very uncomfortable situation, with precious > uncommitted data in the current checkout and the need to change where > the checkout "current commit" points to.
Usually when I find myself in that situation, I just open a new checkout in a separate directory. I usually have several checkouts of any given Fossil repository on each development machine: tip of trunk and a checkout of the last stable release at the very least. drh brought up “stash,” but I don’t like using that for truly precious uncommitted material, since it’s only committed to .fslckout locally, which means a) it isn’t copied off-machine, as checkins are, if your local Fossil clones sync to a remote Fossil server b) if you have a brain fart and nuke the current checkout tree, you lose the associated stash When those worries matter, I generally check my partial feature in as a branch, with the checkin comment noting that the feature isn’t expected to work yet. Having copied the material both into the local repo clone and off-machine, I then feel safe in saying “fossil update” to move the local checkout to a different view. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users