Aaron, it is nothing to do with it. Any contributor could review code. It was a merging problem.
I definitely didn't mean to imply that this particular compilation issue would have been caught by a different reviewer. I'm confident I would not have caught this particular issue myself.
I think this is not true. After a committer provided a patch and a non-committer reviewed it, the same committer could commit the patch.
I think the bylaws are a little ambiguous on the subject. Per the bylaws:
A change made to a codebase of the project and committed by a committer. This includes source code, documentation, website content, etc. Lazy consensus of active committers, but with a minimum of one +1. The code can be committed after the first +1, unless the code change represents a merge from a branch, in which case three +1s are required.
This would seem to imply that a review by a non-committer contributor is non-binding. It does not, however, clear up the issue of whether or not a committer can provide a +1 of their own patch.
FWIW, my understanding is the same as Todd's on this subject.