Thus said Jan Nijtmans on Mon, 25 Nov 2013 17:08:07 +0100: > Any objections to this change? At least it's not dangerous at all: > It's just as easy to "unhide" items than to hide them, just by > removing the "hidden" tag later.
Just some quick observations and questions. First, if I hide a check-in and rename the branch to mistake, when I view the mistake branch using /timeline?r=mistake those items do not show up; of course this is certainly working as it should, but because there is no way to reveal them, I am none the wiser, even though I might actually want to see the mistakes. Second, this will hide something I mark as hidden not only from me but also from everyone because it is synchronized (I'm not suggesting that it should be treated as private, only trying to quantify what the implications are). Which also means that I remove the hidden tag, it will remove it also for you. :-) Third, if I move an entire branch that I consider a mistake to a new branch named ``mistake'' and mark it hidden, the timeline gets weird because it shows a timeline that apparently has no beginning that ends in the recent check-in. Should this be propagating? Fourth, how do I unhide once I have hidden if I don't know the artifact SHA1 of the check-in? I suppose it can be done with the fossil tag command on the command line because I can still see hidden check-ins with the command line timeline. Anyway, there's a bit of quick feedback for now. Andy -- TAI64 timestamp: 4000000052943b94 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
