Before committing I export my code changes in mercurial like
hg diff -r tip > d.diff
or hg export -o d.diff
It creates a nice .diff
When I upload this to review board it returns empty diff file.
File is not empty. How can I fix this?
Before committing I export my code changes in mercurial like
hg diff -r tip > d.diff
or hg export -o d.diff
It creates a nice .diff
When I upload this to review board it returns empty diff file.
File is not empty. How can I fix this?
The workflow you are using (manual hg diff + diff file upload via web browser) is painful and lacks flexibility. When an error occurs, reviewboard is not very helpful in explaining what is going on (to use an euphemism :-).
I suggest two different approaches, which often work out of the box. They are in order of preference from my point of view (that is, I prefer option 1 to option 2).
Use the hgreviewboard extension. This allows to stay in hg for all reviewboard operations: hg postreview ...
will do the diff and upload to reviewboard. hg help postreview
will explain all the options and the advanced usage.
Use the post-review script, provided by reviewboard.org. This approach also allows to avoid the manual steps of the browser upload. The link above has full documentation.