On Wed, Jul 29, 2015 at 12:40:53PM +, Jeremy Stanley wrote:
> On 2015-07-29 10:53:38 +0200 (+0200), Yanis Guenane wrote:
> > On 07/28/2015 07:13 PM, Andreas Jaeger wrote:
> [...]
> > > * If there is a proposed change already for a project, reuse that one
> > > instead of creating a new one?
> >
On Wed, Jul 29, 2015 at 5:40 AM, Jeremy Stanley wrote:
> On 2015-07-29 10:53:38 +0200 (+0200), Yanis Guenane wrote:
> > On 07/28/2015 07:13 PM, Andreas Jaeger wrote:
> [...]
> > > * If there is a proposed change already for a project, reuse that one
> > > instead of creating a new one?
> >
> > I
On 2015-07-29 10:53:38 +0200 (+0200), Yanis Guenane wrote:
> On 07/28/2015 07:13 PM, Andreas Jaeger wrote:
[...]
> > * If there is a proposed change already for a project, reuse that one
> > instead of creating a new one?
>
> I don't have the answer for that I'd have to look. But this should never
On 07/28/2015 07:13 PM, Andreas Jaeger wrote:
> On 07/28/2015 03:35 PM, Yanis Guenane wrote:
>> In PuppetOpenstack we have a common set of filesthat are shared across
>> all our modules.
>> We would like to have an easy way to keep those set of
>> filessynchronized.
>> Based on some discussions o
On 07/28/2015 03:35 PM, Yanis Guenane wrote:
In PuppetOpenstack we have a common set of filesthat are shared across
all our modules.
We would like to have an easy way to keep those set of filessynchronized.
Based on some discussions on #openstack-infra, infra might also be
interested by this prob
In PuppetOpenstack we have a common set of filesthat are shared across
all our modules.
We would like to have an easy way to keep those set of filessynchronized.
Based on some discussions on #openstack-infra, infra might also be
interested by this problematic.
They are (at least) two approaches fo
