2013/12/3 Andy Bradford <[email protected]>:
> For the usage you present it might make more sense if the hidden
> tag were not propagating. It is still achievable with the current
> implementation by simply adding a cancelling tag at the point where you
> don't want it. The only snag is that currently marking a branch as
> hidden will also close it.
You can cancel "hidden" and "closed" in a single operation, it's just two
checkboxes close together on the ci_edit page.
Still, I'm not sure that the "hidden" tag is the best solution for your use: If
you share the repository with others, everyone will see the same
nodes hidden, but other people might be interested in other subsets.
Some filtering method on present tags? .....
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
