On Mon, Nov 26, 2012 at 2:31 PM, Ross Berteig <[email protected]> wrote:
> 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. > I changed the rendering of commit messages at http://www.fossil-scm.org/fossil (and at http://www.sqlite.org/src and several other places) to only decorate hyperlinks and to leave everything else in the commit message unchanged. This occurred in the middle of last week. Everything seems to continue to work fine. There is some occasional mojibake (see http://localhost:591/fossil/timeline?c=bf67db06 for example) but for the most part all the messages appears the same as before. Nobody has complained yet. So I think what you suggest is probably going to be what we end of going with. The next release will have an option on the Admin/Timeline menu to let you enable/disable plaintext commit messages. The default will be off for legacy repositories and on for new repositories. > > -- > Ross Berteig [email protected] > Cheshire Engineering Corp. http://www.CheshireEng.com/ > > > ______________________________**_________________ > fossil-users mailing list > [email protected].**org <[email protected]> > http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
