On Sun, Jul 18, 2010 at 5:39 PM, Igor <xrevol...@gmail.com> wrote:
> I have same ClearCase setup as described in patch of Jan Koprowski -
> Correct me if I wrong, in this patch each repository represents
> clearcase view of specific user (repository_url as defined in Jan's
> patch ) under /view/$user_$module_$branch.
This /view/$user_$module_$branch model looks like misunderstanding.
View for Review Board is another, different dynamic view distinct from
others - central view where all branches of all users are present. You
can get to files on this branches using extended path
/path/to/file@@/main/branch/version. I don't understand why branches
in Your model is different views - not standard ClearCase branch.
> It would be a little bit problematic to set up RB when you have
> hundreds of developers and many modules of different branches in
> ClearCase. What would be the optimal RB configuration of ClearCase
> repository in this case? Wouldn't it be more flexible to set up one
> repository under /view/ (for example) and provide a clearcase view for
> each review request and fetch original file according?
> Thanks, Igor.
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
><> Jan Koprowski
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at