On Thu, Jun 12, 2014 at 12:25 PM, Joe Gordon wrote:
>
> On Jun 12, 2014 9:20 AM, "Jaume Devesa" wrote:
> >
> > Hello all,
> >
> > I've just submitted a patch[1] to solve a bug in Neutron. All the
> third-party plugins has voted as +1 but Jenkins has refused the patch
> because of the '.' dot at
On Jun 12, 2014 9:20 AM, "Jaume Devesa" wrote:
>
> Hello all,
>
> I've just submitted a patch[1] to solve a bug in Neutron. All the
third-party plugins has voted as +1 but Jenkins has refused the patch
because of the '.' dot at the end of the commit summary line.
>
> I know that is my fault, becau
On 06/12/2014 01:07 PM, Jaume Devesa wrote:
> Anita, thanks for the response. My comments inline:
>
>
>
>> Well then we are in a situation where development ceases until the third
>> party systems respond. Which is not a situation we want to put ourselves
>> in. We actually are actively avoidi
Anita, thanks for the response. My comments inline:
> Well then we are in a situation where development ceases until the third
> party systems respond. Which is not a situation we want to put ourselves
> in. We actually are actively avoiding that situation.
>
> I don't mean to run after the c
On 06/12/2014 12:20 PM, Jaume Devesa wrote:
> Hello all,
>
> I've just submitted a patch[1] to solve a bug in Neutron. All the
> third-party plugins has voted as +1 but Jenkins has refused the patch
> because of the '.' dot at the end of the commit summary line.
>
> I know that is my fault, becau
Hello all,
I've just submitted a patch[1] to solve a bug in Neutron. All the
third-party plugins has voted as +1 but Jenkins has refused the patch
because of the '.' dot at the end of the commit summary line.
I know that is my fault, because I should run the ./run_tests.sh -p after
modify the com
