News for hackers. Stuff that matters.
Re:The Carrying-Cost of Code: Taking Lean Seriously by DougBTX on Wednesday May 18, 2011 @08:21AM (#2559856)
You can use svn blame in Eclipse to do some of this.

Instructions: http://stackoverflow.com/questions/223657/svn-blame-in-eclip...

Screenshot: http://wiki.c2b2.columbia.edu/informatics/index.php/Eclipse#...

This will allow you to see commit messages in the code editor on a line-by-line basis. To know if a line of code had a bug in it, you would need to make sure that that sort of information is written into commit messages. Here we use a "Fixes issue #12312" trigger in post commit hook, so that the commit, the code change and the Trac ticket are all linked.

Re:The Carrying-Cost of Code: Taking Lean Seriously by jacabado on Wednesday May 18, 2011 @09:47AM (#2560110)
I also use it (from Visual Studio), but I can't edit while in the "blame" view, it's something outside VS, I guess the Ankh plugin is responsible for that.

What I need is something in the code when I'm editing it, it could be some kind of hint how "old" is the line and if I mouseover it would give me the blame information.

I will check if I can build some plugin for VS or if somebody has done it.