by patch, which
isn't that fast, I guess). Also such data-model allows to see difference
between any versions of a changed file, not only between its "source"
and "target" states. This might be usefull to quickly see if a deve
uned for each database type. Plus it's more
> reusable and other projects could benefit.
yes, I think it would be more reasonable to implement proper support in Django
Evolution. But I don't have enough experience with all that code to solve the
task myself. So I guess I won't
elated_name="review_requests",
but I'm not sure how existing RB DBs should be evolved. Seems that neither
djblets' FakeChangeFieldType nor django_evolution's ChangeField isn't
suitable for the task. Simply add a field and then write a
num IDs) to get
their hands into the code. Hopefully (indeed!) this branch will be merged
back to the official ReviewBoard trunk at a later stage.
Since I don't have enough experience with Reviewboard/Django internals any
help with the stuff will be greatly appreciated. Maybe there's a
On Wednesday 06 May 2009 05:03:17 Marc Hedlund wrote:
> Cool. Thanks much. If I'm successful in getting people going with
> this, I'm sure we'd be willing to help adding more support for git.
Hi!
I'm also interested in a fully functional ReviewBoard / Git interaction.
Currently I'm implementi
On Wednesday 06 May 2009 03:12:58 Christian Hammond wrote:
> We probably want to use os.path.pathsep instead of os.environ.get('IFS')
> anyway.
Christian, the problem is not with IFS, the problem with PATH and other common
environment variables. Actually os.environ doesn't contain anything usefu
ewboard/tmp/egg_cache', 'DJANGO_SETTINGS_MODULE':
'reviewboard.settings'}
Despite such a crippled environment settings git runs just fine
(from /usr/bin/), so I guess it's some Django/FastCGI "security measures".
I'm going to remove the check above or a
d be prepared. Yes, I do remember about your `post-review` advise, but I
didn't have neither svn nor git-svn nor external network connection on the
(virtual) host where I made the changes :)
SIncerely,
Alexey Morozov.
--~--~-~--~~~---~--~~
You received this
On Thursday 30 April 2009 16:04:00 Alexey Morozov wrote:
> I'd like to ask how to properly setup/configure reviewboard in case of
> Apache/FastCGI installation.
It seems that I [partially] solved the installation issues. The problems
noticed so far:
1. For sqlite3 backend settin
I'd like to ask how to properly setup/configure reviewboard in case of
Apache/FastCGI installation.
I have performed all "standard" initial actions and got the reviewboard
initial page but now it says that
Manual server updates required
A recent change requires manual updates to
al format.
Well, it looks like I have another use-case in mind but probably it's more
specific to distributed SCMs (not just git, they all are quite similar in
common operations with code). But let it be the subject for another
message :-)
Yours respectfully,
Alexey Morozov
--~--~
m the repository this shouldn't be too hard to
implement. Another option is to upload a modified file (or files) instead of
a patch. Probably this interface should have SCM-specific parts (or
callbacks) (yes I dream of git commits-based reviews :)
Hello again!
On Thursday 29 January 2009 05:03:05 Alexey Morozov wrote:
> Certainly the change is rather trivial but since I'm almost unfamiliar with
> LDAP-related things I'd like to hear first that there're no other
> considerations not to add the binding.
Also in http
ollaborator) and perhaps I didn't notice
significant issues or maybe current code processing model simply doesn't
allow easy incorporation of these changes.
Best regards,
Alexey Morozov
--~--~-~--~~~---~--~~
You received this message because you are subscribed
considerations not to add the binding.
Respectfully,
Alexey Morozov
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
T
15 matches
Mail list logo
