To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date: 08/24/2014 12:32 PM
Subject: Re: [openstack-dev] [heat] heat.conf.sample is not up to date
On Sun, Aug 24, 2014 at 11:10 AM, Mike Spreitzer mspre...@us.ibm.com
wrote:
What I really
On Aug 24, 2014, at 12:30 PM, Ruslan Kamaldinov rkamaldi...@mirantis.com
wrote:
On Sun, Aug 24, 2014 at 11:10 AM, Mike Spreitzer mspre...@us.ibm.com wrote:
What I really need to know is what to do when committing a change that
really does require a change in the sample configuration file.
On Aug 24, 2014 9:04 AM, Morgan Fainberg morgan.fainb...@gmail.com
wrote:
On Sunday, August 24, 2014, Anne Gentle a...@openstack.org wrote:
I'm following this as well since I have the exact same problem in a
docstring patch for heat.
Keystone saw an oddity with the new sample config
What is going on with this? If I do a fresh clone of heat and run `tox
-epep8` then I get that complaint. If I then run the recommended command
to fix it, and then `tox -epep8` again, I get the same complaint again ---
and with different differences exhibited! The email below carries a
Guessing this is due to the new tox feature which randomizes python's
hash seed.
Excerpts from Mike Spreitzer's message of 2014-08-24 00:10:42 -0700:
What is going on with this? If I do a fresh clone of heat and run `tox
-epep8` then I get that complaint. If I then run the recommended
: [openstack-dev] [heat] heat.conf.sample is not up to date
Guessing this is due to the new tox feature which randomizes python's
hash seed.
Excerpts from Mike Spreitzer's message of 2014-08-24 00:10:42 -0700:
What is going on with this? If I do a fresh clone of heat and run
`tox
-epep8` then I
wrote on 08/24/2014 05:00:21 AM:
From: Clint Byrum cl...@fewbar.com
To: openstack-dev openstack-dev@lists.openstack.org,
Date: 08/24/2014 05:02 AM
Subject: Re: [openstack-dev] [heat] heat.conf.sample is not up to date
Guessing this is due to the new tox feature which randomizes
On Sunday, August 24, 2014, Anne Gentle a...@openstack.org wrote:
I'm following this as well since I have the exact same problem in a
docstring patch for heat.
Keystone saw an oddity with the new sample config generator (changing how
options are sorted and therefore changing the way the
Morgan Fainberg morgan.fainb...@gmail.com wrote on 08/24/2014 12:01:37
PM:
...
Keystone saw an oddity with the new sample config generator
(changing how options are sorted and therefore changing the way the
sample config is rendered). This could be a similar / related issue.
Most of
On Sun, Aug 24, 2014 at 11:10 AM, Mike Spreitzer mspre...@us.ibm.com wrote:
What I really need to know is what to do when committing a change that
really does require a change in the sample configuration file. Of course I
tried running generate_sample.sh, but `tox -epep8` still complains.
Ruslan Kamaldinov rkamaldi...@mirantis.com wrote on 08/24/2014 12:30:04
PM:
From: Ruslan Kamaldinov rkamaldi...@mirantis.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date: 08/24/2014 12:32 PM
Subject: Re: [openstack-dev] [heat
11 matches
Mail list logo
