I think the interface for uploading diffs is very minimalistic and vague
about what to do. The first time, without fail, any of our developers have
tried to use the upload diff interface it has failed to work properly and
results in an error about not being able to apply the diff or being unable
to find the parent revision. This has led to me spending time with each of
these developers to train them how to properly upload diffs. I'd say
something there is very broken if it doesn't work like people are expecting
it to work and it doesn't have a clear explanation of what it is expecting.
Also, if the diff can't be applied properly, it should show an error on the
upload screen about it. They shouldn't have to click "view diff" every
time to make sure it uploaded correctly.
I think saying "the fix for the confusing interface is to not use the
interface and to use the command line tool instead" is not actually a
solution to the problem. It is also not an option for everyone (like our
We have them using reviewboard, but they will only upload their diffs
manually. They have run into this same kind of problem, and it just makes
the tool "overly complicated" and "not worth the time to learn".
Giving this kind of "solution" to a problem is not only insufficient, but
it also shows that the problem is real and the tool is lacking in
functionality and clearness. If it's not understandable and usable, then
it's broken. If it's broken, then it needs to be fixed. The correct "fix"
should not be "use something else".
That being said, it is open source, so I'd love to see the diff of changes
that Will made. They'd probably be helpful for our users too.
On Friday, November 30, 2012 3:53:20 PM UTC-7, David Trowbridge wrote:
> It's correct to upload full diffs. The best way to do this is to use the
> post-review tool, which (with no arguments) will do the right thing.
>> So... don't any users know how whether it's correct to upload full diffs
>> or partial diffs?
>> On Thursday, 22 November 2012 12:44:25 UTC, Will wrote:
>>> Where is it described in the documentation the correct way to make
>>> several diffs and upload them incrementally?
>>> We had a situation where one of our developers only uploaded partial
>>> diffs each time (just the changes since the last time he uploaded a diff),
>>> meaning there was no way to see his complete set of diffs together.
>>> I don't blame him because how was he supposed to know not to do that?
>>> We ended up hacking some extra instructions into the "add review"
>>> template and marking them bold red to try and prevent people doing this.
>>> ReviewBoard assumes all diffs are complete (from first commit to last),
>>> and it figures out the rest, allowing reviewers to easily drill down by
>>> revision if they want.
>>> If any of the uploaded diffs are not complete, then reviewers can
>>> completely miss changes that were made.
>>> a) where is the "right" way to add diffs documented?
>>> b) shouldn't reviewboard make it a lot more difficult to upload diffs
>> 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