svn blame support

[anonymous]

Having svn blame (aka annotate) in the source browser would be real nice.

Thanks for nice job so far, guys.

[cmlenz]

#1215 has been marked as duplicate of this ticket.

[cmlenz]

Experimental implementation of blame support is in source:branches/cmlenz-dev/blame.

[Russ Brown]

For extra brownie points on this, see if there is an svk:merge property somewhere and attempt to resolve merges to find the true authors of the lines merged.

That would be *very* smart.

[anonymous]

#2160 has been marked as duplicate of this ticket.

[anonymous]

Any news on when this is going to be integrated. It would be wonderful to have for the next milestone.

[joe@…]

Sorry update! The last comment was mine, but I forgot to add my email address.

[cboos]

It's currently scheduled for milestone:0.11

cmlenz: can you move your branch to the sandbox, as blame support is also something I'd like to contribute to.

[sven.reimers@…]

I started hacking away at a plugin proving a IHTMLPreviewAnnotator to show blame information along the lines cmlenz provided in his branch. But still there is a problem to access the req object during annotating, just line number and content is passed, additionally the only lineno is requested from inside trac. Anybody any idea if at least the api will be adopted (should not be that complex, since there seems to be only one annotator) - then it should impose no further problem developing this as a plugin (maybe some *.css, etc.). So anybody?

[sven.reimers@…]

Forgot one other problem. The user should be able to select which annotaters are used, so some gui changes would be necessary here as well, but I think cmlenz has already provided some interesting things in his branch as well. Should this be tracked in a different ticket? Maybe this can be fixed in 0.10 time frame (allowing for plugin)

[cboos]

Another duplicate request for this: #3023

[anonymous]

Any news on this? Quite strange for Trac not to have the blame (I prefer the term "praise") feature since cvsweb et al have it.

[dombot@…]

This would be a very handy feature and would be a good potential advantage to convince the dev team from moving from CVS + Bugzilla + Bonsai to Subversion + Trac.

[Trent Apted <tapted@…>]

I am marking a groupwork software project/assignment currently (and have been for about 12 hours straight now). Students must use Trac/SVN and we generate some interesting visualizations from Trac and SVN logs/history

there are technical reports if people are interested: Wattle Tree: What’ll it Tell Us? and [longer] The Big Five and Visualisations of Team Work Activity (the "Big Five" are components of teamwork, according to Salas et al. in the Journal of Small Group Research 36(5), 2005).

However, sometimes you really want the details from an SVN blame.. so.. my fingers are crossed, in the hope 0.11 makes it out before August in time for the next semester :)

[alec.munro@…]

What needs to be done to get this working? I would really like to see more progress on 0.11, and I think I could probably help out with this particulur issue.

[cboos]

#3023 has been marked as duplicate... again. In particular, check this requirement.

[garyo@…]

Not a requirement, but a "would be nice" feature for blame: in Emacs, the blame ("annotate") mode colors source lines by their age. Old lines are blue, new are bright red, and so on. This way the recent changes stand out nicely. I would suggest doing this only for the rev numbers or dates columns in the blame output in trac, since the source lines already have their own syntax colorization. I think a default color scheme of 6 months ago gets blue, today gets red, and linearly in between, would be fine. Not sure arbitrary colors like this are easy with CSS/html though?

[cboos]

See googlegroups:trac-dev:7b0ff9b0f5120f8a

[cboos]

See sandbox/blame.

[cboos]

Replying to garyo@genarts.com:

Not a requirement, but a "would be nice" feature for blame: in Emacs, the blame ("annotate") mode colors source lines by their age. Old lines are blue, new are bright red, and so on. This way the recent changes stand out nicely. I would suggest doing this only for the rev numbers or dates columns in the blame output in trac, since the source lines already have their own syntax colorization.

Done so in r4484, looks great, thanks for the suggestion!

[cboos]

Blame branch merged in r4561.

Issues with the blame feature should be opened as new defect tickets. Feedback and improvements on the feature are welcomed of course, but the base feature is there and seems to be solid.

Note that the TracMercurial plugin (the 0.11 variant, i.e. source:sandbox/mercurial-plugin-0.11) also supports the new blame feature.

[elmarco]

\o/ thanks