Also got some more emails from other users that are generating paths from 
the IDE, so the path in those diffs may be something like 
../root/path/to/ and when they try to submit a diff there is no 
way to get it to work. They were able to make things work in ReviewBoard 
1.6.11 by using . or ./ as the base path. I know that path is a little 
strange because it's essentially going up one from the root directory and 
then back into it, but for some reason about 80% of the people here get 
patch files like that generated from the IDE. Is there any way to make 
these work? I'm having lots of people freaking out on me today because 
things are breaking and they're having to do find and replaces in their 
patch files.

On Thursday, June 11, 2015 at 9:22:17 AM UTC-4, Papaswede wrote:
> I recently upgraded our instance of ReviewBoard from 1.6.11 to 2.0.15. 
> Quite a few people have been reporting issues with uploading diffs that 
> contain ./ as the beginning of the file path and also using ./ as the base 
> directory. They just get an "Unknown Error" on the patch upload screen. For 
> example, if the patch file has this
> --- ./path/to/
> +++ ./path/to/
> that won't work. I've had to ask them to do a find and replace in the file 
> and replace ./ with just / and use / as the basedir. So, the patch file 
> ends up looking like this:
> --- /path/to/
> +++ /path/to/
> Should ./ not work anymore? Also, I know that ideally, we should be using 
> the RBTools to upload files, but it hasn't been approved by our security 
> department as a tool we can have installed yet. So, in the meantime I'm 
> trying to make people's lives as simple as possible.
> Thanks!

Supercharge your Review Board with Power Pack:
Want us to host Review Board for you? Check out RBCommons:
Happy user? Let us know!
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