Code review should use private data

[dustin]

Rather than using tags, I think the code review would be better off having a private set of data within .git that it uses to know what you've done and when.

[nowells]

Let me look into this. I know that within my team at PBS we share code reviews across multiple machines (whoever has the projector connected to their machine at the time) so that was the rational behind tags, but I agree that it can get cluttered. Maybe I should add the ability to configure how the review tags get stored?

Thanks!
Nowell

[dustin]

Configurable might be good. It feels more like a branch than a tag, though, if you have it actually moving along with the code. That might be more acceptable. Tags have this habit of moving around on their own and getting into the way of things.