condemsediffs only needs to be done once. It's optional, but can reduce
database size significantly. You don't need to run a periodic condense
operation. We also condense individual diffs when manually viewing them as
well.
I'll try to find out more info about which versions of MySQL are impacted
MySQL 5.5
Thanks for the explanation
So it is not required to condense diff before db migration, right?
In fact, condense diff happens on the fly. Is there any advantage to do
condense diff from time to time?
On Dec 21, 2016 7:19 PM, "Christian Hammond"
wrote:
> Hey,
Hi Pradeep,
You'll need to follow the guide on writing, packaging, and loading
extensions. This will have to be written as a packaged, loadable extension,
which will be enabled through Review Board. It won't work as a standalone
script, since it won't be running within the context of Review
I used *rbt setup-repo *command and entered yes to all the questions in the
meantime. Did I miss any configuration?
在 2016年12月21日星期三 UTC-8下午3:13:04,Christian Hammond写道:
>
> Hi,
>
> Your .reviewboardrc isn't correct. The BRANCH seems to have an error
> message in it. It should be a single like
Hey,
So the good news is, this is not a corruption issue, nor is it related to
the contents of any of your files.
This error is occurring when saving diff data using our new compressed
storage mechanism. We populate a binary field with compressed diff data
when uploading a new diff, viewing an
Hi Moisei,
There's no support for per-user default reviewers in Review Board itself
(but see below). The rationale is that reviewers tend to pertain to changes
(one group might be appropriate for one repository/path, while another
might be appropriate to another), rather than a reviewer
Hi,
Your .reviewboardrc isn't correct. The BRANCH seems to have an error
message in it. It should be a single like string containing the name of the
destination branch.
This causes a syntax error in the file, preventing the server from being
found.
Christian
On Wed, Dec 21, 2016 at 14:45 许逸斐
Can someone help me resolve this issue?
Here is the content in .reviewboardrc file
在 2016年12月7日星期三 UTC-8下午9:37:38,许逸斐写道:
>
> REVIEWBOARD_URL = "review board URL"
> REPOSITORY = "GitDemo"
> BRANCH = "fatal: ambiguous argument 'HEAD': unknown revision or path not
> in the working tree.
> Use
On Monday, December 19, 2016 at 5:10:15 PM UTC-5, John wrote:
>
> We are using mercurial in our environment and for some reason we are
> seeing a number of __init__.py (blank files for module inclusion in python)
> are being added to our diff file. Here is the process we used to reproduce
>
Hello,
Is there some way to specify a default reviewer group for the user (and not
by the file path as it is mentioned inthe documentation)?
Every time I submit a new issue, I choose my group to be a Reviewer group
and I would like it to happen automatically.
Thank you!
--
Supercharge your
Christian,
As promised, more information in the file attached.
Please HELP, HELP!!
With the utf8 conversion warning, MY CONCERN IS DATA LOSS/CORRUPTION.
If the text contains only plain English, then may be we are fine.
But where multi-byte encoding is required, is there any guarantee
For assigning reviewers, rbt post accepts --target-people and
--target-groups arguments, which each accept a comma-separated list of
usernames/group names, respectively. You can then add --publish to publish
it as well.
-David
On Wed, Dec 21, 2016 at 1:01 AM Vikalp Khandelwal
Hi,
I am using review board for the first time. I am using perforce as my
repository. The steps which I am following are this
1. Create a changelist in perforce
2. Use '*rbt post –d '*
3. Go to the URL generated in browser
4. Add reviewers
5. Publish
I wanted to know if there is any way in
13 matches
Mail list logo