Re: GIT Repository - Local vs Remote Setup

2013-09-19 Thread Atif
Hi guys Apologize if my issue is slightly off than the topic - but I cannot get my Reviewboard to work. My ReviewBoard is on a different server than git server. I have already installed gitweb on git server and can view git code tree through browser using url ( http://[ipaddress]/?p=reponame.gi

Re: GIT Repository - Local vs Remote Setup

2011-01-18 Thread Christian Hammond
You know, it's a good question. We do it by default regardless of the code path, in order to verify that the repository was correctly set up. Maybe we want to revisit that, though I need to think more about it. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.review

Re: GIT Repository - Local vs Remote Setup

2011-01-18 Thread NicBinkley
Thanks for the assistance. I upgraded to 1.5.2 and was able to get the GIT repositories setup in conjunction with SSH keys. I'm still confused as to why ReviewBoard needs git style access when it's setup to use gitweb URLs. On Jan 11, 12:59 pm, Christian Hammond wrote: > Hi, > > The http one

Re: GIT Repository - Local vs Remote Setup

2011-01-11 Thread Christian Hammond
Hi, The http one is just an example. I'll give you a real-world example. http://reviews.reviewboard.org uses the following for our Review Board Git repo: Path: git://github.com/reviewboard/reviewboard.git Mirror Path: g...@github.com:reviewboard/reviewboard.git Raw file URL mask: http://github.co

Re: GIT Repository - Local vs Remote Setup

2011-01-11 Thread NicBinkley
thanks for the reply but something still isn't jiving with our setup. Installation information: ReviewBoard - version 1.5.1 GIT and GITWeb - version 1.7.0.4 We're using gitosis to control access to the repositories. Your example shows an http address for the path - does that mean that ReviewBoard

Re: GIT Repository - Local vs Remote Setup

2011-01-10 Thread Christian Hammond
Hi, First off, can you tell me which version of Review Board you're using? Perhaps the documentation is misleading, but what you should be doing is setting Path to be the "origin" URL. Review Board will use Path to attempt to match the repository provided by post-review (which it gets from doing