On Tue, Jun 11, 2019 at 14:38:31 +0200, Andrea Bolognani wrote:
> On Tue, 2019-06-11 at 14:20 +0200, Peter Krempa wrote:
> > On Tue, Jun 11, 2019 at 13:52:23 +0200, Andrea Bolognani wrote:
> > > On Mon, 2019-05-27 at 15:06 +0200, Andrea Bolognani wrote:
> > > *** PING HERE ***
> >
> > I think you
On Tue, 2019-06-11 at 14:20 +0200, Peter Krempa wrote:
> On Tue, Jun 11, 2019 at 13:52:23 +0200, Andrea Bolognani wrote:
> > On Mon, 2019-05-27 at 15:06 +0200, Andrea Bolognani wrote:
> > *** PING HERE ***
>
> I think you can push it under the "nobody cares" rule.
That's a weird way to spell
On Tue, Jun 11, 2019 at 13:52:23 +0200, Andrea Bolognani wrote:
> On Mon, 2019-05-27 at 15:06 +0200, Andrea Bolognani wrote:
> > We only do this when performing operations that the
> > corresponding Ansible module doesn't support, so we know
> > what we're doing and don't want warnings to show up.
On Mon, 2019-05-27 at 15:06 +0200, Andrea Bolognani wrote:
> We only do this when performing operations that the
> corresponding Ansible module doesn't support, so we know
> what we're doing and don't want warnings to show up.
>
> Note that while only the dnf and yum modules complain at
> the
We only do this when performing operations that the
corresponding Ansible module doesn't support, so we know
what we're doing and don't want warnings to show up.
Note that while only the dnf and yum modules complain at
the moment, we might as well use warn=no everywhere so that
we're already
