Re: forcing post-review to disregard current working directory

2013-05-23 Thread Kudrettin Güleryüz
. Add your virtualenv to Pydev interpreters list and select that one as the default interpreter. In my case selecting all libraries available simply worked with RBTools development. On Wed, Mar 20, 2013 at 12:11 PM, Matthew Woehlke mwoehlke.fl...@gmail.comwrote: On 2013-03-20 10:13, Kudrettin

Re: forcing post-review to disregard current working directory

2013-03-20 Thread Kudrettin Güleryüz
-- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mar 19, 2013, at 4:24 PM, Matthew Woehlke mwoehlke.fl...@gmail.com wrote: On 2013-03-19 10:16, Kudrettin Güleryüz wrote: I have cloned the latest RBTools from github. After

forcing post-review to disregard current working directory

2013-03-19 Thread Kudrettin Güleryüz
Hello, I have cloned the latest RBTools from github. After I make changes to postreview.py regarding perforce, I'd like to test my changes but postreview.py assumes I'll be submitting reviews regarding RBTools itself. Can I override this behavior? If not please suggest your development workflows.

Re: post-review created 2 reviews for the same change list number

2013-03-19 Thread Kudrettin Güleryüz
Hi, Can there be two different Perforce servers involved with the two submissions? one submission using perforce-main vs another using perforce-backup for instance... Kudret On Tue, Mar 19, 2013 at 10:45 AM, Steve seide.al...@gmail.com wrote: Any thoughts on the duplicate review problem?