With [#6610] changing Trac import to use HTML as its basis, the cross-reference links will be handled nicely with no special parsing of them (they're already links).
So this will just need to be applied to commit messages. See also [#6111] which is to have commit messages not be handled as full markdown, but just make their artifact references be links. --- ** [tickets:#6140] Support trac commit/ticket syntax** **Status:** open **Labels:** import trac **Created:** Thu Apr 18, 2013 09:30 PM UTC by Dave Brondsema **Last Updated:** Tue Aug 27, 2013 07:10 PM UTC **Owner:** nobody Tickets & wiki imported from trac [#4213] and [#6139] as well as SVN commits that have trac syntax for referencing tickets and svn revisions should still work in Allura. Examples: * `#123` for tickets (no brackets) * `r456` for svn revision * https://sourceforge.net/apps/trac/gfarm/changeset/8016 * A less frequent format: * `ticket:100` * `comment:13:ticket:408` * `source:gfarm_v2/trunk/server/gfmd/inode.c@6697#L3233` We can't change content during import since it's in SVN commit messages too. A regex should be easy to identify these. TBD: allow this simpler syntax all the time, or just for trac-imported content via some flag? --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
