Thus said Jan Nijtmans on Tue, 26 Nov 2013 12:50:52 +0100: > At this moment, only single nodes can be hidden, that's intended. I > see no problems making it propagating, it would make it easier to hide > big parts without anyone noticing. I'm not sure we want to encourage > that.
Tough choice. Do we make avoiding the strange timelines easier or do we make it easy to hide entire timelines? Here are some of the states that the timeline can get into (some with propagate and some without): http://fossil.bradfords.org:8080/timeline Notice that branch five has a strange break in it (this was done using your UI change). The mistake branch was also done using the UI change, and both have timelines that have no beginning. I hid the trunk using the command line by adding a propagating hidden tag to it. Also, this tag propagates to branches so there is also a hidden branch (and a handful of check-ins) that are no longer seen. If you open this fossil in the UI that doesn't have your change, a lot more will be visible. > Well, the event which added the "hidden" tag is still visible in the > timeline, so you can always get the SHA1 from there. Yes, I discovered this after I sent the email. Thanks. Along with the button to reveal hidden timeline items, should the ability to always show hidden items be a preference in Admin->Timeline? Kind of like the ``Show version differences by default'' option. Thanks, Andy -- TAI64 timestamp: 400000005294d6d8 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
