- Original Message -
> From: "Maru Newby"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> On Oct 29, 2014, at 12:25 PM, Steve Gordon wrote:
>
> > - Original Message -
> >> From: "Maru Newby"
> >> To: "OpenStack Development Mailing List (not for usag
- Original Message -
> From: "Sean Dague"
> To: openstack-dev@lists.openstack.org
>
> On 10/29/2014 07:25 AM, Steve Gordon wrote:
> > - Original Message -
> >> From: "Maru Newby"
> >> To: "OpenStack Development Mailing List (not for usage questions)"
> >>
> >>
> >> Am I the only
On Oct 29, 2014, at 12:25 PM, Steve Gordon wrote:
> - Original Message -
>> From: "Maru Newby"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>>
>> Am I the only one wondering whether introducing arbitrary tagging into our
>> commit messages sets a bad prece
On 10/29/2014 07:25 AM, Steve Gordon wrote:
> - Original Message -
>> From: "Maru Newby"
>> To: "OpenStack Development Mailing List (not for usage questions)"
>>
>>
>> Am I the only one wondering whether introducing arbitrary tagging into our
>> commit messages sets a bad precedent? Or
- Original Message -
> From: "Maru Newby"
> To: "OpenStack Development Mailing List (not for usage questions)"
>
>
> Am I the only one wondering whether introducing arbitrary tagging into our
> commit messages sets a bad precedent? Or was there a discussion on this
> topic that I misse
Yeh, this seems incredibly poluting, don't do this. That's not something
I want in our long term git history without conversation about the
policy. Every other Impact flag that we use in OpenStack had a pretty
long conversation about it's addition.
The issue arrises because the NFV team has create
Am I the only one wondering whether introducing arbitrary tagging into our
commit messages sets a bad precedent? Or was there a discussion on this topic
that I missed?
Maru
On Jun 17, 2014, at 2:27 PM, Sylvain Bauza wrote:
> Hi,
>
> There is an action for creating a Gerrit dashboard to sh
Hi,
There is an action for creating a Gerrit dashboard to show all
NFV-related specs and patches.
As it requires to have a specific label for discriminating them, I'm
adding "NFVImpact" in all the patches proposed in [1].
The side effect is that it creates another patchset and so runs another
Jenk
