Comment #3 on issue 3171 by RBTools: A critical bug for determining SCM type?

I'm talking about the repositories, not for individual users. A Git repository using Review Board needs a .reviewboardrc file to link it up (unless your wrapper script is doing something specialized, in which case it can pass that parameter). It's not much different than needing to configure the Review Board URL and repository path.

The problem boils down to how Perforce handles configuration. It needs to be overridden somewhere. We can't hard-code the order, as that's just a bandaid around the real problem. As we've seen from other enterprise-sized companies, there's other combinations of repositories being used that cause the same sorts of problems (Subversion repos embedded inside Git, for instance, or Git inside of Subversion). There's no order we can pick that solves every situation. The only real way to solve this is the option we provide, which is what other companies of this size use.

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to