Hi Tino, This greatly depends on the revision control system, and isn't really specific to Review Board. If you have separate independent changes you want to post to review, you need to do multiple checkouts or use some sort of a patch-management system (like Quilt). This is a more general issue of how you do development on multiple things at once when dealing with the same files.
Christian -- Christian Hammond - chip...@chipx86.com VMware, Inc. On Mon, Dec 29, 2008 at 5:10 PM, Tino Breddin <tino.bred...@googlemail.com>wrote: > > Hi, > > I am wondering how you handle changes in the same file which don't > really fit into the same review request. So you would have a change > for which you create a review request. Then you change other things in > the same file and would like to create a review request for these > changes only. Is it necessary to create branches for each of the > changes, wait until the review is complete, commit changes and then > merge branches into trunk? > > Thank, Tino > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "reviewboard" group. To post to this group, send email to reviewboard@googlegroups.com To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en -~----------~----~----~----~------~----~------~--~---
