Hi Bruce,
Yeah, this is due to the new commit ID field. We associate the commit ID
with a review request and treat it like Perforce change numbers, where
there's a one-to-one mapping of review request and commit. This is crucial
for a number of features we have planned for improved DVCS support.
I can't actually think of why someone might want to create two reviews from
the same commit.
--
Bruce
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at
I've been setting up Review Board 2.0 RC2, and found I got an HTTP 500
error with an IntegrityError when trying for a second time to post a review
from a git repository using 'rbt post'.
The first time, I'd forgotten to set the Mirror Path in the repository
configuration, so i got:
ERROR:
I've checked and this appears to be a regression from at least 1.7.9. It
used to be possible to run the same 'rbt post' command in a git repo twice
and end up with two reviews.
--
Bruce
On Thu, Apr 17, 2014 at 8:34 PM, Bruce Cran bruce.c...@gmail.com wrote:
I've been setting up Review Board