Really good question! 
I also encounter the same problem. Developers dont want to wait until the 
previous review passed to work on the next issue. 
One solution I think is, once a review passed, apply that review`s patch 
file to a new working copy without touching what you are currently working 
on, then commit it. After the commit is done, you can keep going.
But the pinpoint is, when you create a code review, the paths in the patch 
file is NOT your local path but some paths in the SVN server(I am using 
SVN). That prevents me to apply patches(wrong patch error). 
I have no idea why the review board changes the paths from local to remote 
server, at least it should keep the local working copy`s path.

Here`s a example of what those paths look like:

--- /trunk/ReviewBoardTest/src/     (revision 166)
+++ /trunk/ReviewBoardTest/src/     (working copy)     you 
see here? The working copy is locally, but the review board still changes its 
path to remote server.

Get the Review Board Power Pack at
Sign up for Review Board hosting at RBCommons:
Happy user? Let us know at
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to