Jay wrote:
On Sep 21, 12:11 pm, Chris Clark chris.cl...@ingres.com wrote:
It looks like p4 is claiming there is a perforce repo in the svn
location. A quick hack/test would be to modify postreview to check svn
first. I.e. hack the SCMCLIENTS def.
Let's assume this suggestion
The way to do this would be to edit postreview.py either by adding some sort
of directive as I think you are suggesting or by customizing for your
site/usage.
If it were me, I'd edit the SCMCLIENTS list definition (I've actually done
this for our site, I have customization for VMS so svn isn't
I have post-review installed on windows and have successfully been
creating RB requests against perforce. We also have SVN projects, but
when I try to use post-review against them it wants to talk to
perforce instead. For instance if I enter:
post-review --server=http://somehost/reviewboard
Jay wrote:
I have post-review installed on windows and have successfully been
creating RB requests against perforce. We also have SVN projects, but
when I try to use post-review against them it wants to talk to
perforce instead. For instance if I enter:
post-review
On Sep 21, 12:11 pm, Chris Clark chris.cl...@ingres.com wrote:
It looks like p4 is claiming there is a perforce repo in the svn
location. A quick hack/test would be to modify postreview to check svn
first. I.e. hack the SCMCLIENTS def.
And where would the SCMCLIENTS.def be located? Is this
in file postreview.py somewhere in
/usr/lib/python2.x/site-packges/rbtools/ (this could be zipped so You
probably must use some smart editor which allow change files in zipped
archives)
On Tue, Sep 21, 2010 at 10:43 PM, Jay jayki...@gmail.com wrote:
On Sep 21, 12:11 pm, Chris Clark
On Sep 21, 12:11 pm, Chris Clark chris.cl...@ingres.com wrote:
It looks like p4 is claiming there is a perforce repo in the svn
location. A quick hack/test would be to modify postreview to check svn
first. I.e. hack the SCMCLIENTS def.
Let's assume this suggestion actually works since it
