Hello Christian,

OK, thank you for clearing that up. I thought the repository was
suppose to indicate for which project you're requesting a review. Is
there anywhere to indicate to which project a patch applies? Thank
you.

--
Arthur Kalmenson



On Wed, Dec 3, 2008 at 5:28 PM, Christian Hammond <[EMAIL PROTECTED]> wrote:
> Review Board only needs one repository per actual repository. Projects in
> Subversion exist as subdirectories inside a repository.
>
> So for example, in the case of Review Board, we have one repository pointing
> to the Review Board SVN server. Any diffs against Review Board itself is
> generated in /trunk/reviewboard, and as such /trunk/reviewboard is used as
> the "base diff path" (the path relative to the root of the repository where
> the diff was generated). If we posted a change against the website, we'd use
> a base diff path of /trunk/website, on the same repository.
>
> Hope that clears things up?
>
> Christian
>
> --
> Christian Hammond - [EMAIL PROTECTED]
> VMware, Inc.
>
>
> On Wed, Dec 3, 2008 at 12:08 PM, Arthur Kalmenson <[EMAIL PROTECTED]>
> wrote:
>>
>> Hello everyone,
>>
>> After setting up reviewboard and reading the following document:
>> http://code.google.com/p/reviewboard/wiki/Adding_Repositories we are
>> under the impression that reviewboard assumes there is one repository
>> per project (with Subversion). Because our team has all of its
>> projects in one repository, we can only have one repository and have
>> to use a different base diff path for each review. Is there another
>> way of doing this?
>>
>> --
>> Arthur Kalmenson
>>
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to