Hi,
I encounter a problem of post-review cannot figure out the right base path.
I have checked the svn URI of Review Board and .reviewboardrc.
What can I do for the next?
the svn repository is like this,
project - trunk
my .reviewboardrc,
REPOSITORY = 'http://localhost/svn/project/1024GB'
REVI
Hi,
I have a problem looks like about base path when using post-review and I
cannot figure it out how to make
post-review using the right base path. I had tried to change the path of
REPOSITORY to "http://svn.repos"; both in
the configuration of ReviewBoard and .reviewboardrc, and change the na
Hi,
It would be very convenient to see which review has some open issues in it
in a glance. Is there any way to see it in the dashboard view?
Thanks in advance:
Gyula
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know a
Hi,
I'm getting a confusing error when I try to run post-review
Failed to execute command: ['git', 'config', 'core.bare']
I've tried running this command directly in the repository (a non-bare
clone) and it simply returns. I'm not sure what response the script is
expecting. I'm using git ver
Not at this time. It can be added (please file a feature request), but
first we'd need to start storing that state and keep it up-to-date. We
don't do that today in a way that's efficient.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc.
I download the source of rbtools and find something made the base path
blank.
At line 69 of
https://github.com/reviewboard/rbtools/blob/master/rbtools/clients/git.py,
the value of "self.options.repository_url" in my case will be the value found
by "git svn info".
the condition of "not self.op
I think the interface for uploading diffs is very minimalistic and vague
about what to do. The first time, without fail, any of our developers have
tried to use the upload diff interface it has failed to work properly and
results in an error about not being able to apply the diff or being unabl
You do not need them to run post-review from the command line themselves. Our
users work on windows (server is on unix) and I have a script that does all the
"hard" work. All the users need to do is right click on the main source folder
and choose between these two options (added to the list via
Hi Brian,
I'm sorry you took the answer of "use post-review" as a kind of "this is
the only solution because we don't want to work on this page" answer. I do
think there's much room for improvement on this page.
I'd like to go over what I see as a couple of the main challenges we face
that preven
