Thus said to...@acm.org on Mon, 16 Jun 2014 00:14:20 +0300: > OK, my problem is not so much with the committing act per se (of > non-working code,) -- besides, you do have to have a mechanism of > adding your changes, even WIP ones, in the repo -- it's with ending up > with a history / timeline that is full of 'incomplete attempts', > instead of clean code commits, and (for now, at least) no way > to filter by, say, tag, so you have to see every little silly > modification to any (yet) useless file.
You can use the ``hidden'' tag to tuck away silly attempts or commits that were simply mistakes. In the Fossil source repository, code changes that were wrong (or silly) get assigned to the mistake branch and sometimes marked ``hidden'' so they don't show up in the timeline. Here are some examples: http://www.fossil-scm.org/index.html/timeline?n=20&y=ci&c=2013-12-20+17:04:49 http://www.fossil-scm.org/index.html/timeline?n=20&c=2014-01-16+11:56:09&y=ci If you click the ``Unhide'' button on those pages, a branch of development will appear that was not there before. Andy -- TAI64 timestamp: 40000000539e78fc _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
