Changes between Version 4 and Version 5 of RevtreePlugin/Limitations

Show
Ignore:
Author:
eblot (IP: 82.251.8.51)
Timestamp:
02/20/07 17:08:58 (8 months ago)
Comment:

Grammar fixes

Legend:

Unmodified
Added
Removed
Modified

  • RevtreePlugin/Limitations

    v4 v5  
    1 = Technical details about the limitations of the plugin = 
     1= Technical details about the plugin limitations = 
    22 
    33Several requests have been made to enhance the plugin. 
    1717=== Version control backend === 
    1818 
    19 The plugin could be enhanced to support other version control backend, such as 
     19The plugin could be enhanced to support other version control backends, such as 
    2020Hg ([http://www.selenic.com/mercurial/ Mercurial]). I do not plan to support  
    2121other backends for now. 
    2626   properties: each successive commit increases the revision number by one. It 
    2727   does not use the revision date for ordering changesets. This would need to  
    28    be changed for Hg. Would it makes sense that the Trac VC abstraction layer  
     28   be changed for Hg. Would it make sense that the Trac VC abstraction layer  
    2929   provide a sort method for ordering changesets? 
    3030 * SVN changesets are integers. The changeset graphic elements are easily  
    31    rendered as the integers have a short representation (few characters).  
    32    Hg uses wider changeset identifiers, which make them unsuitable for being  
    33    displayed in the existing changeset graphic elements of the revtree graph.  
    34    Suggestions are welcomed! [[BR]] See ([t:ticket:3533 #3533]) for a related ticket. 
     31   rendered as the integers have a short representation (a few characters).  
     32   Hg uses wider changeset identifiers, which make them unsuitable for  
     33   display in the existing changeset graphic elements of the revtree graph.  
     34   Suggestions are welcome! [[BR]] See ([t:ticket:3533 #3533]) for a related ticket.