On 11/22/2012 5:05 AM, Richard Hipp wrote:
Fossil understands check-in comments and ticket text to be Wiki/HTML. Let's say that the mimetype is "text/x-fossil-wiki". This approach worked well for us on CVSTrac (which was where many of the ideas in Fossil originated) because it allowed hyperlinks to other check-ins, tickets, wiki, etc to be embedded in the check-in comment text.
> ....
For commit messages, I frequently use a message like "See ticket [deadbeef]" when the checkin is directly related to a ticket. Personally, I don't think I've ever wanted to use [] in a commit message for anything else. But then, I try hard to use tickets to hold the larger issue discussions and keep commit messages short and to the point. Since the wiki render also displays the links to closed tickets distinctly, this works out nicely.
Changing commit messages to a pure text/plain interpretation would break that usage.
Unless you consider a ticket or checkin uuid in brackets to also be a valid URL, if the referenced artifact exists. That would have the benefit of providing some visual feedback for mis-typed artifact names by not making those be links.
That said, I do support the idea that the commit comment get a very light handed markup treatment. It fits my personal workflow well if the commit comments are expected to be short and largely free of markup.
-- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
