---Message d'origine-
De : Andreas Jaeger [mailto:a...@suse.com]
Envoyé : jeudi 5 février 2015 10:54
À : MICHON Anthony; openstack-infra@lists.openstack.org
Objet : Re: [OpenStack-Infra] Code Review needs another verified
On 02/05/2015 09:58 AM, MICHON Anthony wrote:
> Thanks for your resp
nvoyé : mercredi 4 février 2015 17:03
> À : openstack-infra@lists.openstack.org
> Objet : Re: [OpenStack-Infra] Code Review needs another verified
>
>
>
> On Wed, Feb 4, 2015, at 07:51 AM, MICHON Anthony wrote:
>> Hi all
>>
>> We committed some change on a newl
ailto:cboy...@sapwetik.org]
Envoyé : mercredi 4 février 2015 17:03
À : openstack-infra@lists.openstack.org
Objet : Re: [OpenStack-Infra] Code Review needs another verified
On Wed, Feb 4, 2015, at 07:51 AM, MICHON Anthony wrote:
> Hi all
>
> We committed some change on a newly created pro
On Wed, Feb 4, 2015, at 07:51 AM, MICHON Anthony wrote:
> Hi all
>
> We committed some change on a newly created project and the review
> (https://review.openstack.org/#/c/147182/
> ) needs another +1 verified, Jenkins gave +1 but how give another +1 ?
> It seems that others projects do not nee
Because your change depends on an abandoned change, so you need to
rebase to get rid of the dependency.
On 02/04/2015 07:51 AM, MICHON Anthony wrote:
Hi all
We committed some change on a newly created project and the review
(https://review.openstack.org/#/c/147182/
) needs another +1 veri
Hi all
We committed some change on a newly created project and the review
(https://review.openstack.org/#/c/147182/
) needs another +1 verified, Jenkins gave +1 but how give another +1 ?
It seems that others projects do not need a +2 verified to pass to the next
step (example here : https://re
