Comment #2 on issue 3190 by d...@cabo.dk: Cannot checkout rbtools
repository using Mercurial
http://code.google.com/p/reviewboard/issues/detail?id=3190
If I come up with a patch to fix this, would you accept it? I could either
make it extract the repository once per test run, or simply
Updates:
Status: NeedInfo
Comment #3 on issue 3190 by chip...@gmail.com: Cannot checkout rbtools
repository using Mercurial
http://code.google.com/p/reviewboard/issues/detail?id=3190
Possibly, but it does make development more painful for us.
I'd like a better sense for why you're
Comment #4 on issue 3190 by d...@cabo.dk: Cannot checkout rbtools
repository using Mercurial
http://code.google.com/p/reviewboard/issues/detail?id=3190
Well, I've been looking into making it work with Mercurial and Perfarce, a
Perforce integration extension for Mercurial, but with no luck
Comment #5 on issue 3190 by chip...@gmail.com: Cannot checkout rbtools
repository using Mercurial
http://code.google.com/p/reviewboard/issues/detail?id=3190
Perforce would be good. Right now, there's a lot of work going on with
Mercurial support, so it's basically getting a complete
Comment #6 on issue 3190 by d...@cabo.dk: Cannot checkout rbtools
repository using Mercurial
http://code.google.com/p/reviewboard/issues/detail?id=3190
Well, I can always push from Mercurial to Git and post the review from
there… (Adding support for hg-git would be neat, but I haven't need
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3191 by bod...@gmail.com: consequent searches crash
with 'initVM() must be called first' error
http://code.google.com/p/reviewboard/issues/detail?id=3191
*** READ THIS BEFORE POSTING!
***
*** You must complete this form in
Comment #7 on issue 3190 by d...@cabo.dk: Cannot checkout rbtools
repository using Mercurial
http://code.google.com/p/reviewboard/issues/detail?id=3190
Here's an example patch: https://reviews.reviewboard.org/r/5257/
--
You received this message because this project is configured to send
Updates:
Status: Confirmed
Comment #1 on issue 3191 by chip...@gmail.com: consequent searches crash
with 'initVM() must be called first' error
http://code.google.com/p/reviewboard/issues/detail?id=3191
PyLucene changes their API basically all the time. You need to have a
pretty
Updates:
Status: WontFix
Comment #2 on issue 3191 by trowb...@gmail.com: consequent searches crash
with 'initVM() must be called first' error
http://code.google.com/p/reviewboard/issues/detail?id=3191
In fact, given that we're replacing the backend entirely, and pylucene bugs
are
Updates:
Status: Fixed
Comment #2 on issue 1702 by trowb...@gmail.com: Allow reviews of files, not
just of commits
http://code.google.com/p/reviewboard/issues/detail?id=1702
This is now fixed in the master branch (and will ship in 2.0 beta 2). Text
files can be added as attachments
Comment #1 on issue 1757 by iander...@mac.com: MySQL support on Mac OS X
Server requires downloading the developer pieces
http://code.google.com/p/reviewboard/issues/detail?id=1757
Mac OS X Server switched over to Postgres awhile ago so there's probably no
point in fixing this now.
--
Updates:
Status: WontFix
Comment #2 on issue 1757 by trowb...@gmail.com: MySQL support on Mac OS X
Server requires downloading the developer pieces
http://code.google.com/p/reviewboard/issues/detail?id=1757
Sounds good to me.
--
You received this message because this project is
12 matches
Mail list logo
