Re: Issue 2465 in reviewboard: For non owned review - fix error message in Review Board post-review tool

2012-02-06 Thread reviewboard
Comment #3 on issue 2465 by sudhir.s...@gmail.com: For non owned review - fix error message in Review Board post-review tool http://code.google.com/p/reviewboard/issues/detail?id=2465 Hi David post-review -r ID (where ID is not owned). FYI, we use subversion and I don't feel this issue

Re: Issue 2465 in reviewboard: For non owned review - fix error message in Review Board post-review tool

2012-02-06 Thread reviewboard
Updates: Status: Fixed Comment #4 on issue 2465 by trowb...@gmail.com: For non owned review - fix error message in Review Board post-review tool http://code.google.com/p/reviewboard/issues/detail?id=2465 Thanks! Fixed in master (7570943). -- You received this message because you

Re: Issue 2465 in reviewboard: For non owned review - fix error message in Review Board post-review tool

2012-02-05 Thread reviewboard
Updates: Status: NeedInfo Comment #2 on issue 2465 by trowb...@gmail.com: For non owned review - fix error message in Review Board post-review tool http://code.google.com/p/reviewboard/issues/detail?id=2465 How are you invoking post-review? Is this with perforce? -- You received

Re: Issue 2465 in reviewboard: For non owned review - fix error message in Review Board post-review tool

2012-01-25 Thread reviewboard
Comment #1 on issue 2465 by sudhir.s...@gmail.com: For non owned review - fix error message in Review Board post-review tool http://code.google.com/p/reviewboard/issues/detail?id=2465 Better diagnostic for non owned review update is as below: if not server.info.supports_changesets or

Issue 2465 in reviewboard: For non owned review - fix error message in Review Board post-review tool

2012-01-24 Thread reviewboard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2465 by sudhir.s...@gmail.com: For non owned review - fix error message in Review Board post-review tool http://code.google.com/p/reviewboard/issues/detail?id=2465 * NOTE: Do not post confidential information in this bug