I can spend a little time working on the patch and testing. I'm not
bzr expert, but I use it daily. Would that be ok?
Who needs to do the full review?
Do you know when the freeze should be done? Ie, when should I poke at
this issue again?
On Jun 26, 3:37 am, Christian Hammond <chip...@chipx86.com> wrote:
> Hi Dan,
> We need to do a full review and make sure it's suitable. I don't know if the
> original author is still around (there weren't any updates made after the
> current reviews), but we'd need someone familiar with bzr to help finish up
> any changes and test them.
> Right now, we're freezing RBTools while some restructuring work finishes up
> in a branch. It's too tedious to keep things in sync right now. Once that
> work is in, we can start accepting patches again.
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
> On Sat, Jun 25, 2011 at 3:29 PM, Daniel Benamy <dben...@gmail.com> wrote:
> > Hi,
> > Adding bzr support to post-review seems to be in limbo. There's a
> > patch for it at
> > and a thread about it at
> > There's a comment in the review that says that changing the regex to
> > BRANCH_REGEX = r'\w*(branch|branch root): (?P<branch_path>.+)$'
> > makes it work. That regex matches the output of my "bzr info" too and
> > I think I saw one or two comments on other lists of it working for
> > people but it was a while ago.
> > Is there anything holding up the merging of that patch + new regex?
> > Thanks!
> > Dan
> > --
> > Want to help the Review Board project? Donate today at
> > Happy user? Let us know athttp://www.reviewboard.org/users/
> > -~----------~----~----~----~------~----~------~--~---
> > To unsubscribe from this group, send email to
> > reviewboard+unsubscr...@googlegroups.com
> > For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at