We hit this problem as well. Some of our developer teams tend to use IDE's such as eclipse etc instead of command line. So they usually create differential revisions through patch diffs instead of using archanist. A speedy fix would be appreciated.

We'd like tagstops be respected if at all possible. Short of that, we'll take a configurable setting that allow us to replace a tab with a number of spaces. Thanks.

My task description gave details on the steps that the user managed to assign himself the reviewer of his own revision. I was able to follow the same steps to recreate the problem.

I set it to false which stops a user from accepting his own revision. This works fine. But it should also stop a user from making himself the reviewer. This does not work. If we allow a user to be his own reviewer but not allow him to accept his own revision, then his only choice is abandoning his review. This does not make sense.

I don't see the logic. I can make myself the reviewer for my own revision but as a reviewer, I cannot accept the revision. So I am only allowed to abandon my revision even if I am happy with my code changes?