I've recently set up ReviewBoard with Perforce configured for pre- commits. Perforce allows source files to be checked out by multiple developers at the same time. If one developer submits a file for review and then a second developer checks in their changes to the same file before the code reviewer has had a chance to look at the first developers changes, the diff will be out of date. The diff stored in ReviewBoard uses the rev of the source code in Perforce at the time the review was submitted. Is there any workaround for this situation? Is there any way for ReviewBoard to at least flag the reviewer that they're not reviewing the latest revision of the source code from source control. Or maybe have ReviewBoard notify the developer that they need to resolve changes and re-submit the file for review?
Thanks, Glen -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
