Thank you Graeme for your thought-provoking post. It seems most challenges and rebuttals have played out.
If anyone was mining this thread for ways to improve fossil, I think they'd see 2 things: 1) Fossil's ticket handling is not best-in-class. What are the key features that would make it at least competitive? What features does it have that are already better than most? (I've never used tickets, although the integrated ticket system was one of my reasons for moving from Hg to Fossil.) 2) The wiki is not best-in-class. What are the key features it needs? (Merging of changes is certainly one that I see. If multiple people are working on the train to/from work, you don't want "last committer wins" in your wiki. This is the point of DVCSs.) ../Dave _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
