http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Never had a chance to use this, but i keep it bookmarked just in case. [http://code.google.com/p/rietveld/](http://code.google.com/p/rietveld/)http://ayende.com/4759/code-review-tools#comment5http://ayende.com/4759/code-review-tools#comment5Tue, 25 Jan 2011 13:46:26 GMTI like to use Codebase HQ for private team based projects - [http://www.codebasehq.com/](http://www.codebasehq.com/) - lots of nice features although, I have not seen specific line notes like you are showing here. http://ayende.com/4759/code-review-tools#comment4http://ayende.com/4759/code-review-tools#comment4Sat, 22 Jan 2011 17:36:00 GMTThe only thing I still need is pull requests on existing issues, then there is nothing that stops me to do the next larger project we tackle with the aid of a private repository in github :) http://ayende.com/4759/code-review-tools#comment3http://ayende.com/4759/code-review-tools#comment3Sat, 22 Jan 2011 16:19:23 GMTshouldn't the 't' be a 'w' ;) http://ayende.com/4759/code-review-tools#comment2http://ayende.com/4759/code-review-tools#comment2Sat, 22 Jan 2011 15:35:32 GMTThat's my way to see how RavenDB is working. Whenever you commit something to the repository, I inspect the changes and try to understand them. This way I can see if it might break my code, and I think I learn something too. Additionally I may see an error on occasion as the one above, and a direct comment on GitHub seemed to be the most appropriate way for reporting. http://ayende.com/4759/code-review-tools#comment1http://ayende.com/4759/code-review-tools#comment1Sat, 22 Jan 2011 11:19:07 GMT