Matt Good wrote: > Tim Hatch wrote: > >> I notice that there's a cmlenz-dev/blame branch that hasn't been >> touched in about a year. This would be pretty much impossible to merge >> with trunk at this point, so what does everyone think about creating a >> new one under sandbox for collaborative work[1]? >> > > +1. The blame support itself would be handy, but it'll also enable > other useful annotations, such as enabling Bitten to provide a view of > the test coverage for a file. >
I'm also OK to revive this effort, of course, but this is a quite complex topic. There's the annotation part, which are perhaps better done in the mimeview refactoring branch, as we go. Then, there's the annotate algorithm itself. There are several approaches here: make it backend specific, make it generic (at the cache level). Note that this operation is going to be _very_ inefficient if done the naive way (i.e. get the full text of all the involved revision, and see what changed by ourselves). So probably better is to do it the backend specific way. For Mercurial, it's near to trivial to reuse the existing filectxt.annotate() method and get the needed sequence of (changeset, line) out of it. For Subversion, it looks a lot more complex to get it done right, as we'd need to use the svnclient API and I'm not sure if all the bits and pieces needed are available to the bindings. -- Christian || --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
