sorry, introduced pdb.set_trace() by mistake into the patch, plz delete
this line, and use the patch as below:
diff --git a/reviewboard/scmtools/clearcase.py
b/reviewboard/scmtools/clearcase.py
index 19ea97f..35888e3 100644
--- a/reviewboard/scmtools/clearcase.py
+++
On Saturday, February 4, 2012 6:24:11 AM UTC+1, Christian Hammond wrote:
Don't we have another thread on this?
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
2012/2/1 深圳手机(王) 8257...@qq.com
On Jan 23, 2013, at 12:42 AM, km karl.mau...@gmx.de wrote:
On Saturday, February 4, 2012 6:24:11 AM UTC+1, Christian Hammond wrote:
Don't we have another thread on this?
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. -
Hi Christian,
I imagined that this would be your response, but I wanted to bring it
forward so that others ( and you ) are aware of it. Out of curiosity,
will you always send timestamps in UTC ( ending in 'Z' ) or will you
use the timezone modifier of the Reviewboard installation, e.g. +01:00
?
I had some trouble with ReviewBoard 1.7.1 and the httpd config it generated.
Fedora 18 ships with Apache httpd 2.4, I had to adjust the following line:
Options -Indexes FollowSymLinks
Fixed line:
Options -Indexes +FollowSymLinks
This has been fixed in ReviewBoard 1.7.2,
I'm not sure how to run as a rb shell, I was just running in python
On Tuesday, 22 January 2013 11:07:28 UTC-8, Christian Hammond wrote:
Running that likely wont give you an accurate repro case. There's a lot
that goes on to configure what's used for SSH and how the key is loaded.
Are you
Sorry for the late reply. Don't know what was broken. I just removed, then
reinstalled the mercurial package and everything is working again. Thanks
for your help!
Randy
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at
Dear all
(This is my first message here).
I will use post review (committed in Subversion).
While reviewing if I find a bug how can I indicate that a review has a bug?
I want to close the review with a kind of bug-tag.
for example, I need another close status, bug (currently two status -
Do you mean that the posted code has a bug?
The intent behind review requests is that they remain open and iterate
until the code is either committed or discarded. If you want to indicate
that the review request has a bug, post a review with an open issue. The
poster then has the opportunity to
On 2013-01-23 02:48, Hyunil Shin wrote:
I will use post review (committed in Subversion).
While reviewing if I find a bug how can I indicate that a review has a bug?
I want to close the review with a kind of bug-tag.
for example, I need another close status, bug (currently two status -
There's a fix coming for the console error bug in IE. (Good ol IE… only browser
that gets this wrong.).
What versions of IE are you using there?
We're *strongly* encouraging modern browsers (not IE) from here on out, and
will be aggressively dropping support for older versions of IE going
Thanks for the prompt reply, using IE 7.
On Wed, Jan 23, 2013 at 3:28 PM, Christian Hammond chip...@chipx86.comwrote:
There's a fix coming for the console error bug in IE. (Good ol IE… only
browser that gets this wrong.).
What versions of IE are you using there?
We're *strongly*
I'll see about spending a little it of time on it when I've solved a couple
other bugs on my plate, but IE7 is one of the versions we've dropped, due to
how difficult it is to get it to render correctly, and its lack of support for
standards we're going to be making more use of.
Christian
--
Thank for your reply.
yes. My case is to review posted code.
So, you mean that if a posted code (review request) has a bug, just still
open the request and add an issue. That's good idea.
Additionally, I want to distinguish between not-reviewed request and
request with a bug.
(I have regular
We have an open feature request for adding a column which would display the
open issues. For now, the best way is probably to add the dashboard column
which lists the number of reviews--at least then, you'll be able to see
when something has been looked at or not.
-David
On Wed, Jan 23, 2013
Thank you~
Using the number of reviews may be good.
I will discuss with other developers.
On Thursday, January 24, 2013 9:12:25 AM UTC+9, David Trowbridge wrote:
We have an open feature request for adding a column which would display
the open issues. For now, the best way is probably to add
If you run the rb-site command I mentioned, you should get that shell.
I've been actively working on this problem, but it is very strange... I'll let
you know when I finally have something to test.
Christian
On Jan 23, 2013, at 8:59, Alex Edwards edwards.a...@gmail.com wrote:
I'm not sure
Anything I can do about it or am I out of luck until 1.7.3?
Ian
On Tuesday, January 22, 2013 8:44:52 AM UTC-8, christop...@gmail.com wrote:
Same problem on Fedora 18 / reviewboard 1.7.2
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user?
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2874 by brodie...@gmail.com: Reviewboard 1.7.2 requires pytz-2012j
http://code.google.com/p/reviewboard/issues/detail?id=2874
* NOTE: For customer support, please post to *
*
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2875 by wclah...@hotmail.com: Something broke! (Error 500)It
appears something broke when you tried to go to here. This is either a bug
in Review Board or a server configuration error. Please report this to your
20 matches
Mail list logo
