Thus said Nikita Borodikhin on Fri, 21 Oct 2016 16:02:33 -0000: > == change sets - preparing the change == > > I often end up having several sets of unrelated changes. For example, > one set is my temporary change to the build system to disable some > things to make build process faster, but these changes are not > intended to come into the end product and are not to be committed.
You could simply open a new checkout and keep unrelated changes in different checkouts of your repository. For example, fossil new /tmp/test.fossil mkdir /tmp/tinker && cd /tmp/tinker && fossil open /tmp/test.fossil mkdir /tmp/explore && cd /tmp/explore && fossil open /tmp/test.fossil mkdir /tmp/maybe && cd /tmp/maybe && fossil open /tmp/test.fossil Etc... > svn cl syntax is inconsistent, but I root for the idea to label > connected files for the commit/review purpose and I would love to have > something like that in Fossil By ``label connected files'' I assume you mean related changes. If you're already doing the above suggestion, there's always the option to stash the changes. Andy -- TAI64 timestamp: 40000000580a7267 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
