[asterisk-dev] Using ReviewBoard to review work in developer branches (caveats)

Terry Wilson twilson at digium.com
Wed Nov 26 15:32:03 CST 2008

> If you are working on code in a developer branch and want to get it
> posted for review, today your only option is to merge those changes  
> into
> a clean checkout of the baseline branch and then use 'svn diff' or
> 'postreview.py' to create the diff. However, if your developer branch
> contains *new* files, the diff won't include them!

I've always just done a svn diff https://origsvn.digium.com/svn/asterisk/trunk 
  https://origsvn.digium.com/svn/team/twilson/calendaring > diff.txt,  
then manually removed any configure changes or if anything has snuck  
through because since the last automerge.  Seemed to work fine for  
me...or am I missing something?

More information about the asterisk-dev mailing list