On Fri, Mar 2, 2012 at 2:38 PM, Anton Cohen wrote:
>
> On Fri, Mar 2, 2012 at 10:58 AM, Tucker wrote:
>
>> Should I do a whole new install and migrate the DB?
>>
>> On Tue, Feb 28, 2012 at 2:43 PM, Tucker wrote:
>> > I decided to try and build pylucene again on CentOs 5.2. I kept
>> > running
Thanks, I got some response from TM, they said I need to buy some
service for a dedicated server.
On Wed, Feb 29, 2012 at 11:01 PM, Stephen Gallagher
wrote:
> On Tue, 2012-02-28 at 23:59 -0800, David Trowbridge wrote:
>> I won't rule it out entirely because I haven't tried, but I think it's
>> pr
As I said, there are a few approaches. Ordered in terms of simplicity:
- Mark the file as binary in perforce.
- Tell users to remove the file from their changelist during review (it's not
possible for people to review megabytes of text, and reviewing things which are
automatically generated gener
Thanks David,
While separately we are not doing any pre or post commit review its only
the tool which post-review does that it. Yes the file is very large so what
could be done here, are their any enhancement we need to do in our review
board server or client to make this thing work. Please sugges
Are you doing pre- or post-commit reviews?
post-review will try to send diffs for all non-binary files. There's no way to
exclude individual files except for temporarily removing them from the
changelist. If your .STEP files are actually large binaries, I'd suggest
changing the filetype in perf
Hi,
We are trying to check in the changes to perforce, but we see post-review
got stuck, it happens for only one file with extention (.STEP) which is
having headType as 'ctext', I would like to know if review board impose any
restriction while posting the diff to review board for certain set of
fi
On Fri, Mar 2, 2012 at 10:58 AM, Tucker wrote:
> Should I do a whole new install and migrate the DB?
>
> On Tue, Feb 28, 2012 at 2:43 PM, Tucker wrote:
> > I decided to try and build pylucene again on CentOs 5.2. I kept
> > running into problems with python2.4, so I built jcc against python2.6
Should I do a whole new install and migrate the DB?
On Tue, Feb 28, 2012 at 2:43 PM, Tucker wrote:
> I decided to try and build pylucene again on CentOs 5.2. I kept
> running into problems with python2.4, so I built jcc against python2.6
> (ActivePython). I eventually got it working (using open
