There are two (or three, depending on how you count) indentations styles
mixed together in this one logical line of code, which are further mixed
with two methods of closing parens and curly braces.
Besides being difficult to read, the mixture resulted in an off-by-one
error that isn't caught by the version of hacking that Jenkins is using,
but is caught by the latest.
Reviewed: https:/ /review. openstack. org/118894 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=5157bc62bf3 b7aa3792f8148c4 2bc7213b607068
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5157bc62bf3b7aa 3792f8148c42bc7 213b607068
Author: Dolph Mathews <email address hidden>
Date: Wed Sep 3 15:53:20 2014 -0500
use one indentation style
There are two (or three, depending on how you count) indentations styles
mixed together in this one logical line of code, which are further mixed
with two methods of closing parens and curly braces.
Besides being difficult to read, the mixture resulted in an off-by-one
error that isn't caught by the version of hacking that Jenkins is using,
but is caught by the latest.
Change-Id: Idab3c80c720e0b fd5741dc9e07f84 1b5ac270960
Closes-Bug: 1363019