While it no doubt works, it's a bandaid. The core problem needs to somehow be addressed, or it will just happen again down the road. At some point, we'll no longer have a hard-coded list of repository types. They'll be scanned instead, likely alphabetically.
A fix for the issue treating svn repo as perforce by mistake
Review Request #3525 — Created Nov. 17, 2012 and submitted
This issue occurred when post-review in an svn repo while p4 client is also installed. Since p4 tool is checked in prio, the svn repo will be treated in p4 way and an error message will be prompted. It would be better we consider svn whose metadata is stored locally in prio to p4 whose metadata is stored on server side.