Hi all, I'm also interested in this feature since the group I'm working with uses git submodules and we are interested in a coherent review. But since there was no interest from review board developers so far I wanted to ask: where should I start to implement a proof of concept for git? I'm interested only to extend it for patches.
A single review can have only one associated repository in the sql schema it seems, this can probably be easily changed. But then I would have to create a special format of patches so that each file is attributed to a repository so that the review board could show the differences. Is such a patch format already available by some tools? And let's say I manage all that: review has multiple repositories and I have a patch which has them associacted with each of those repositories. Is there anything else that should be taken care of? Cheers, Radek On Thursday, 23 November 2017 20:15:14 UTC+1, Eric Chamberland wrote: > > Hi, > > I just jump into this conversation to say that we have the same problem > here: we have to manage a "review" as a set of changes across multiple > repositories. > > So +1 for this feature to be implemented. > > Thanks, > > Eric > > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "Review Board Community" 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.
