[Trac-tickets] Re: [The Trac Project] #1032: [patch] Recognize Subversion-style revision numbers (rNNNN) as a changeset link

[The Trac Project]

#1032: [patch] Recognize Subversion-style revision numbers (rNNNN) as a changeset
link
-------------------------+--------------------------------------------------
       Id:  1032         |      Status:  assigned                
Component:  wiki         |    Modified:  Fri Jan 28 07:35:15 2005
 Severity:  enhancement  |   Milestone:  0.9                     
 Priority:  normal       |     Version:  0.8                     
    Owner:  cmlenz       |    Reporter:  rmunn at pobox.com         
-------------------------+--------------------------------------------------
Old description:

> Currently (as of Trac 0.8), the Wiki recognizes [N] as a changeset link,
> and will recognize that syntax in commit log messages. But the
> traditional format for writing Subversion revision numbers is rNNNN. See,
> for instance, http://svnbook.red-bean.com/en/1.1/ch04s04.html, where
> commit log messages like "Merged my-calc-branch changes r406:480 into the
> trunk" or "Undoing change committed in r303" are given as examples.
>
> I propose that WikiFormatter.py should recognize not just [N] format, but
> also rNNNN format, as a changeset link.

New description:

 Currently (as of Trac 0.8), the Wiki recognizes [N] as a changeset link,
 and will recognize that syntax in commit log messages. But the traditional
 format for writing Subversion revision numbers is rNNNN. See, for
 instance, http://svnbook.red-bean.com/en/1.1/ch04s04.html, where commit
 log messages like "Merged my-calc-branch changes r406:480 into the trunk"
 or "Undoing change committed in r303" are given as examples.

 I propose that !WikiFormatter.py should recognize not just [N] format, but
 also rNNNN format, as a changeset link.

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/1032>
The Trac Project <>