#1099 Don't cache "last commit to modify" information on trees and blobs directly

v1.0.0
closed
Rick Copeland
sf-2 (994)
SCM
nobody
2015-08-20
2010-10-29
Rick Copeland
No

This needs to be stored on a per-repo basis, not globally, as files which coincidentally have the same contents will only have one commit listed as the last to modify them (and that last commit to modify them may even be from a different repo).

Related

Tickets: #1085

Discussion

  • Rick Copeland - 2010-10-29
    • status: open --> in-progress
    • assigned_to: Rick Copéland
    • custom_field__size: --> 1
    • custom_field__milestone: backlog --> nov-01
     

  • Rick Copeland - 2010-10-29
    • status: in-progress --> closed
     

Log in to post a comment.