On Wed, Dec 15, 2010 at 05:14:08PM +0100, Remigiusz Modrzejewski wrote: > 1) work freely on my big change, committing atomic changes > fl commit --private > fl commit --private > [...] > fl commit --private > 2) prepare to make a "real commit" > fl up trunk > fl merge private > 3) make sure everything works as expected, commit to the world > fl commit > > This feels intuitive and does not leave space for disaster. Furthermore, at > step 3 you can see an aggregated diff of the final shape of your big change. > And yes, I think of it as a patch queue. > > How would a "stash" add value? Apart from the fact, that you have to clone to > a new repo to get rid of old private commits.
Big change doesn't necessarily mean "can be cut into smaller pieces". Especially in that case the incremental committing doesn't really work. Joerg _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
