There have been no changes to this as yet. We'd like to address this
eventually but it's a very difficult thing to address in a generic way, and
for the time being we have other priorities.

-David


On Fri, Sep 20, 2013 at 4:32 AM, Luboš Račanský <lubos.racan...@gmail.com>wrote:

> I have the same question. Is there any way how to merge (from ReviewBoard)
> after acceptance of review?
>
>
> On Friday, May 3, 2013 11:05:07 PM UTC+2, mamta.n...@gmail.com wrote:
>>
>> Hey David,
>> This is an older post but i"m actually looking for exactly these things
>> currently and was wondering if these features have been built into
>> reviewboard now  / via plugins or are they still in pipeline?
>>
>> Thanks,
>> M
>>
>> On Wednesday, April 20, 2011 3:34:59 PM UTC-7, David Trowbridge wrote:
>>>
>>> #2 would be great; I know a lot of people have requested the ability to
>>> have some indication that the patch submitted will (a) apply cleanly and
>>> (b) build (maybe even including automated testing).
>>>
>>> #1 is often requested, but it's something which we've been wary of
>>> because of the complexities of user authentication, audit chains, and the
>>> abilities it would introduce to break things. It would be a cool feature,
>>> but I think we'd need to approach it carefully.
>>>
>>> -David
>>>
>>>
>>> On Thu, Apr 14, 2011 at 10:19 AM, Jan Koprowski <jan.ko...@gmail.com>wrote:
>>>
>>>> Hi,
>>>>
>>>> Recently i look at Gerrit - review tool dedicated for git guys. Two
>>>> things bring my attention:
>>>>
>>>> 1) Gerrit try to merge code automatically after review. This is great
>>>> ability. As far I'm aware when merge won't end with success developer get
>>>> message to rebase their code and send to review again. It will be cool to
>>>> get something similar at reviewboard. I think this approach will for for
>>>> Git and probably for Mercurial too.
>>>>
>>>> 2) Build system integration. I saw Hudson & Gerrit integration which
>>>> assume additional field for build system which check is project build with
>>>> new versions or not. It is well  exposed at http://source.android.com/*
>>>> *source/life-of-a-patch.html<http://source.android.com/source/life-of-a-patch.html>.
>>>> Will be something nice to make accessible some by API "checkbox field" for
>>>> build system and approach such workflow in reviewboard - optional ofcourse.
>>>>
>>>> What do You think?
>>>>
>>>> Regards,
>>>>
>>>> Jan
>>>>
>>>> --
>>>> Want to help the Review Board project? Donate today at
>>>> http://www.reviewboard.org/**donate/<http://www.reviewboard.org/donate/>
>>>> Happy user? Let us know at 
>>>> http://www.reviewboard.org/**users/<http://www.reviewboard.org/users/>
>>>> -~----------~----~----~----~--**----~----~------~--~---
>>>> To unsubscribe from this group, send email to
>>>> reviewboard...@googlegroups.**com
>>>> For more options, visit this group at http://groups.google.com/**
>>>> group/reviewboard?hl=en<http://groups.google.com/group/reviewboard?hl=en>
>>>
>>>
>>>  --
> Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
> ---
> Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
> ---
>
> Happy user? Let us know at http://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to