Thanks for the tip! it's probably my .reviewboardrc file...

On Nov 11, 1:13 am, Christian Hammond <chip...@chipx86.com> wrote:
> Hi,
>
> This would only happen if:
>
> 1) You hard-coded the repository path in your copy of post-review.
> 2) You have a .reviewboardrc sitting in some parent directory pointing to
> the Perforce repository path.
> 3) Your local CVS checkout is somewhere inside your Perforce checkout.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
>
> On Fri, Nov 6, 2009 at 4:14 PM, mary <ciaom...@gmail.com> wrote:
>
> > I setup a new CVS repository on my ReviewBoard server (adding to the
> > existing Perforce repositories already setup.)
>
> > I'm trying to use 'post-review' to post a CVS review now, but it's not
> > working. It's using the repository path for the Perforce repository.
>
> > Is there a way in post-review to explictly set the repository_path
> > that should be used?
>
> > Or is this a server side issue? Do I need to configure something
> > additionally to support running more than one repository? The only
> > thing I've done so far is to add a new repository in the admin GUI
> > called "cvs".
>
> > Thanks!
>
> > Using RB v1.0.5.1 on Centos5.3
> > > To unsubscribe from this group, send email to
> > reviewboard+unsubscr...@googlegroups.com<reviewboard%2bunsubscr...@googlegroups.com>
> > For more options, visit this group at
> >http://groups.google.com/group/reviewboard?hl=en
> > -~----------~----~----~----~------~----~------~--~---
--~--~---------~--~----~------------~-------~--~----~
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to