Comment #1 on issue 1918 by [email protected]: git diffs are not parsed correctly
http://code.google.com/p/reviewboard/issues/detail?id=1918
It worked if I touched up the diff to look exactly like a subversion diff. I think the key was adding "(revision ####)" and "(working copy)" after the filenames.
Obviously, this is not a feasible long-term solution, because it requires way too much manual work for each diff.
-- You received this message because you are subscribed to the Google Groups "reviewboard-issues" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
