Changes between Version 1 and Version 3 of Ticket #368


Ignore:
Timestamp:
Jan 12, 2009, 5:52:05 AM (14 years ago)
Author:
Peter Johansson
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #368

    • Property Milestone changed from svndigest 0.7 to svndigest 0.x+
  • Ticket #368 – Description

    v1 v3  
    77There are two places to reduce number of ''svn blame'':
    88
    9  1. The first place is in the output (as described in ticket:358). If we wanna keep the output as now, we should at least move the ''svn blame'' call so it is only done once for each File and then pass around the SVNblame object to the several outputs.
     9 1. '''obsolete''' The first place is in the output (as described in ticket:358). If we wanna keep the output as now, we should at least move the ''svn blame'' call so it is only done once for each File and then pass around the SVNblame object to the several outputs.
    1010
    1111 2. In the parsing, one ''svn blame'' is called for every rev the File has been modified. However, this happens twice since it happens for both SVNblame and SVNadd. If we could re-structure the code, so only one ''svn blame'' call is needed and that information can be passed to both classes.