From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: kdevops@lists.linux.dev, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH 2/2] ansible.cfg: generate an ansible.cfg file in TOPDIR
Date: Fri, 29 Aug 2025 09:59:28 -0700 [thread overview]
Message-ID: <aLHccG2DiBVi_9LT@bombadil.infradead.org> (raw)
In-Reply-To: <05f60242-0623-438e-9f68-a1c180934396@kernel.org>
On Fri, Aug 29, 2025 at 09:39:41AM -0400, Chuck Lever wrote:
> On 8/29/25 7:23 AM, Luis Chamberlain wrote:
> > On Thu, Aug 28, 2025 at 04:28:27PM -0400, Chuck Lever wrote:
> >> From: Chuck Lever <chuck.lever@oracle.com>
> >> +config ANSIBLE_CFG_FILE_DEFAULT
> >> + bool "Use a sensible default location for the ansible.cfg file"
> >
> >> + default N
> >
> > defaults are always n, so this line can be removed.
> >
> >> + help
> >> + When this option is set to Y, kdevops creates an ansible.cfg
> >> + in a sensible default location, using the settings defined
> >> + in this Kconfig menu.
> >
> > Why would we not want this by default?
>
> Because N matches the current behavior.
>
> But I would prefer Y, actually.
I think its safe to use Y.
LUis
next prev parent reply other threads:[~2025-08-29 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 20:28 [RFC PATCH 0/2] Set TOPDIR at run time Chuck Lever
2025-08-28 20:28 ` [RFC PATCH 1/2] Set TOPDIR_PATH and generate its sha256sum " Chuck Lever
2025-08-29 11:19 ` Luis Chamberlain
2025-08-29 13:38 ` Chuck Lever
2025-09-01 11:29 ` Daniel Gomez
2025-08-28 20:28 ` [RFC PATCH 2/2] ansible.cfg: generate an ansible.cfg file in TOPDIR Chuck Lever
2025-08-29 11:23 ` Luis Chamberlain
2025-08-29 13:39 ` Chuck Lever
2025-08-29 16:59 ` Luis Chamberlain [this message]
2025-09-01 12:00 ` Daniel Gomez
2025-09-01 15:03 ` Chuck Lever
2025-09-01 17:07 ` Daniel Gomez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aLHccG2DiBVi_9LT@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox