Hi,
You will need cvs on the server, definitely. The 1.1 alpha series won't let
you create a CVS repository without having it. You'll also need it on the
client running post-review.
The base path should be None in this case. It's really only needed for
Subversion.
Can you show me the Repository
OK, I am using ReviewBoardV1.05 My Repository setting on Administrator
UI is as follows:
Name: NewProductCode
Path: :perver:jo...@192.168.3.151:/export/home/
cvsroot
Mirror Path: /cvs_gz/export/home/cvsroot
Repository Type: CVS
With your help, I can use WebUI pre-commit review now. But why the
post-review can't find Base
Path of repository?
Regards!
On Dec 15, 5:35 am, Christian Hammond chip...@chipx86.com wrote:
Hi,...
read more
You will need cvs on the server, definitely. The 1.1 alpha series won't let
you
Another problem is When I am using CVS repository, the debug info
report is :
svn info
On Dec 15, 5:35 am, Christian Hammond chip...@chipx86.com wrote:
Hi,...
read more
You will need cvs on the server, definitely. The 1.1 alpha series won't let
you create a CVS repository without having
Hi, Christian,
I have changed the source of Postreview.py, and now the post-
review can work fine. I found that in class CVSClient, the function
get_repository_info, It use socket.getfqdn(host) to replace the host
of repository_path; So I managed to keep the repository_path
unchanged. Though
The getfqdn call essentially gets the fully-qualified domain (so,
foo.example.com instead of just foo, for instance).
We recently added support for Perforce to check against all aliases,
including what's reported locally. We should add this for CVS as well.
I don't really know what you mean by
Hi, Christian,
Thanks for replay. I said rebuild because I am using the directly
installed ReviewBoard, I don't know it's compiling form souce process.
If I want to change some python source code of ReviewBoard, Then how
to compile the ReviewBoard again, and do I need to reinstall the
compile
Oh, I see. Thank you very much！
Best Regards!
On 12月15日, 下午2时13分, Christian Hammond chip...@chipx86.com wrote:
Review Board is in Python, and doesn't actually need to be compiled.
However, to do any real development (with the expectation of contributing
back to the project) you'll need to
Hi, I had type http://192.168.3.20:8080/reviewboard/api/json; the web
shown is the login page, But the title of this web reports:404 Page
Does Not Exist | Review Board
On Dec 12, 5:25 pm, Christian Hammond chip...@chipx86.com wrote:
The .post-review-cookies.txt file is where the HTTP cookie with
The .post-review-cookies.txt file is where the HTTP cookie with the
authentication token is stored. This prevents needing to log in after the
first post-review (generally).
If you go to http://192.168.3.20:8080/reviewboard/api/json/ in your browser,
what do you see?
The two paths you saw should
Oh, I see, Thank you. And I have another problem. I think the post-
review is good tool because it need no hand generated diff file. But I
had installed the post-review on my Windows machine as client and I
want to use it to link both RB server on a Linux machine and CVS
server on another Linux
And there may be some configuration error in my rb-site. But I have no
idea about that: Because I have no root permission on RedHat system,
So I had use Include statement in apache httpd.conf file, to import
the apache-modpython.conf file of rb-site. and that turns out
accessable through Web-UI of
Hi, all,
I am now confused by the relationship between CVS and RB. RB has
provieded post-commit review, there is no direct relationship between
RB review and CVS submit. So it looks like that the review process and
CVS operation are independent. But why the RB need a repository
setting? Is the
13 matches
Mail list logo
