You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Cory Johns <ma...@users.sf.net> on 2013/11/07 22:35:32 UTC
[allura:tickets] #6140 Support trac commit/ticket syntax in commit messages
- **QA**: Cory Johns
---
** [tickets:#6140] Support trac commit/ticket syntax in commit messages**
**Status:** code-review
**Labels:** import trac
**Created:** Thu Apr 18, 2013 09:30 PM UTC by Dave Brondsema
**Last Updated:** Fri Nov 01, 2013 05:16 PM UTC
**Owner:** Tim Van Steenburgh
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.