Comment #1 on issue 1918 by git diffs are not parsed correctly

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
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to