+1.
On Wed, Aug 27, 2014 at 10:25 PM, Kyle Mestery mest...@mestery.com wrote:
On Wed, Aug 27, 2014 at 8:24 AM, Gary Kotton gkot...@vmware.com wrote:
Hi,
A few cycles ago the Nova group decided to remove @author from copyright
statements. This is due to the fact that this information is
Hi,
A few cycles ago the Nova group decided to remove @author from copyright
statements. This is due to the fact that this information is stored in git.
After adding a similar hacking rule to Neutron it has stirred up some debate.
Does anyone have any reason to for us not to go ahead with
On Wed, Aug 27, 2014 at 8:24 AM, Gary Kotton gkot...@vmware.com wrote:
Hi,
A few cycles ago the Nova group decided to remove @author from copyright
statements. This is due to the fact that this information is stored in git.
After adding a similar hacking rule to Neutron it has stirred up some
T hese should all be comment changes, so there should be no impact. While
I agree that it is late for J3, IMO this is the type of change
(minor/comment only) that should be OK J4 rather than wait for Kilo.
On Wed, Aug 27, 2014 at 7:25 AM, Kyle Mestery mest...@mestery.com wrote:
On Wed, Aug 27,
On Aug 27, 2014, at 2:27 PM, Mandeep Dhami
dh...@noironetworks.commailto:dh...@noironetworks.com wrote:
T hese should all be comment changes, so there should be no impact. While I
agree that it is late for J3, IMO this is the type of change (minor/comment
only) that should be OK J4 rather
I do agree with Kyle. There is no rush for having this code merged in
order to a void multiple rebase work for the other patches.
Edgar
On 8/27/14, 9:25 AM, Kyle Mestery mest...@mestery.com wrote:
On Wed, Aug 27, 2014 at 8:24 AM, Gary Kotton gkot...@vmware.com wrote:
Hi,
A few cycles ago the
