Hi Griffin,

That's an interesting way to work on a branch and then merge to trunk (but 
don't commit) then post a pre-commit review. I'll try it out here, thanks 
for the idea!

We've found another way around the original problem here too: the root 
cause of the problem is an rbt diff can't fully resolve moved svn files, 
however, an svn diff can. So we've found that performing an svn diff across 
the revision range, dumping this to file, and then doing an rbt post 
--diff-filename .... works really well. 

I've seen quite a few questions posted on here about how to handle svn 
moved files and this method has certainly worked across all of the problem 
repos I've come across.

Interestingly, we use loads of svn externals here but I've not had a single 
problem with them! 

Supercharge your Review Board with Power Pack: 
Want us to host Review Board for you? Check out RBCommons: 
Happy user? Let us know! https://www.reviewboard.org/users/
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 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to