Comment #3 on issue 2159 by trowb...@gmail.com: when there are other commits meanwhile, they show up in delta-diffs
http://code.google.com/p/reviewboard/issues/detail?id=2159
The problem is that if a new revision of the diff comes off a different revision of the code, there's no way for us to know if it'll apply cleanly on top of what r1 was based on (and if the files themselves have changed in between, where you're seeing changes in the interdiff, it probably won't).
What I mean about making sure you don't sync is that you base your updated diff off the same revision of the code as the first revision. With svn you can do this by updating your checkout to that revision (svn update -r <rev>), and with git you can just avoid rebasing your branch, and then post-review with --parent set to the parent of the change (assuming master has been updated).
-- You received this message because you are subscribed to the Google Groups "reviewboard-issues" group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
