For what it’s worth my group transitioned from GitWeb to cgit a couple of years
ago. The performance increase was dramatic. I imagine there are other
git-to-http options out there as well.
Terry
From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On
Behalf Of David
Hi Michael,
Sounds like some state got messed up on your end, too.
Can you find the script I had Risha run (the one with the Version import)?
Any other info you can provide that we went through earlier on the thread
would also help.
Basically... That KeyError means you have state missing that
You can install any version of Reviewboard using easy_install. Look at the
documentation here:
https://www.reviewboard.org/docs/manual/2.0/admin/installation/development-releases/#installing-development-releases
For example to install Version 1.6:
easy_install -f
John,
rb-gateway has not had an official release, but there are a few people who
have built it and are running it. It's designed to be run on the same
server as your central git repository, so it doesn't use a clone at
all--it's therefore equivalent to how people use gitweb right now, but it
has
Is there a straightforward way to determine the location of the offending
key?
I wonder whether I can circumvent some issues by upgrading incrementally to
intermediate versions of ReviewBoard -- I'm taking a pretty big leap. I
have installed via easy_install, which has of course taken the
Thanks for the quick reply David, that helps a lot.
Is rb-gateway released yet? I can't find a lot of info about it yet. Will
it handle this problem of keeping the git repo's up to date? I could
imagine if there is a service between ReviewBoard and the Git repo, when rb
asks rb-gateway for a
Review Board uses the repository to fetch the "original" version of the
files for each change in order to construct the side-by-side view (since
the diffs that are uploaded are just unified diffs with limited context).
Updating every 5 minutes is likely to work almost all the time, but if
someone
On the reviewboard site it says "In order to work with Review Board, a
local clone needs to be kept in sync regularly. It should either have
direct access to a central Git server, or it needs to be updated on every
commit to the central Git server."
My question is why? What features will break
I've noticed that the --diff-only option to rbt post is no longer working
the way it used to with Perforce. It may be trying to be too clever. If I
create a review with this perforce change description:
Description:
Bogus review request to test --diff-only option
Using
$ rbt post CL
