On Wed, 9 Jan 2013 06:37:54 -0500, Richard Hipp <[email protected]> wrote: >I'd do it this way: > > fossil commit -m "Failed Attempt" --branch dead-end > fossil up prev > >That will save your failed attempt in your history forever. The failed >attempt will be on a branch, however, out of the way. I avoid putting >non-working code on the trunk, since that will cause problems for future >bisects. > >If you don't what to save your failed attempt forever, but just want to >keep it around for a few days (or weeks) in case you later decide to go >back it it, I'd save it in the stash instead: > > fossil stash save > >The previous command will save all your changes in a stash entry, then >revert your check-out to its pristine state.
Thanks much for the feedback. I guess the time has come to start using branching :-) I didn't know about "stash" but I'd rather keep all attemps with no limit, so I guess I'll use branching instead. Ramon below mentions "fossil update trunk" instead of "fossil update prev": Does it make a difference? _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
