This is where the repository information you provide in the administration
UI comes into play. Review Board downloads each file from the diff from the
repository. It then makes a copy of the file, applies the patch, and
generates its own diff (which contains information beyond what a standard
diff can provide). The result of that is what gets sent to the user's
browser. That code all lives in reviewboard/scmtools/* and
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
2010/1/25 qhlonline <qhlonl...@163.com>
> Hi, all.
> I am using Reviewboard 126.96.36.199 and my code repository is "CVS". I had
> previously thought the post-review tool had only passed a "unified cvs diff"
> file to Reviewboard server, So on the "view diff" page, users can only see
> part of the file (where change take place). And I found now, I can click the
> "*Expand changes* " link to see the whole file. But I don't know how did
> the basic code file was provided to Reviewboard server. I don't think the
> file was posted by "post-review" tool, because I can create ReviewRequest
> through WebUI, And there I can only upload an "cvs diff' file.
> So, can any body told me how did Reviewboard get the basic file of
> the review reqeust? and where can I read the source code about it?
> Best Regards!
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at