From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrea Claudi <aclaudi@redhat.com>
Cc: netdev@vger.kernel.org, Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
bridge@lists.linux-foundation.org,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH iproute2-next 1/2] configure: add the --color option
Date: Fri, 15 Sep 2023 08:59:12 -0700 [thread overview]
Message-ID: <20230915085912.78ffd25c@hermes.local> (raw)
In-Reply-To: <844947000ac7744a3b40b10f9cf971fd15572195.1694625043.git.aclaudi@redhat.com>
On Wed, 13 Sep 2023 19:58:25 +0200
Andrea Claudi <aclaudi@redhat.com> wrote:
> This commit allows users/packagers to choose a default for the color
> output feature provided by some iproute2 tools.
>
> The configure script option is documented in the script itself and it is
> pretty much self-explanatory. The default value is set to "never" to
> avoid changes to the current ip, tc, and bridge behaviour.
>
> Signed-off-by: Andrea Claudi <aclaudi@redhat.com>
> ---
More build time config is not the answer either.
Don't want complaints from distribution users about the change.
Needs to be an environment variable or config file.
next prev parent reply other threads:[~2023-09-15 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 17:58 [PATCH iproute2-next 0/2] configure: add support for color Andrea Claudi
2023-09-13 17:58 ` [PATCH iproute2-next 1/2] configure: add the --color option Andrea Claudi
2023-09-15 15:59 ` Stephen Hemminger [this message]
2023-09-15 18:23 ` David Ahern
2023-09-15 19:52 ` Andrea Claudi
2023-09-13 17:58 ` [PATCH iproute2-next 2/2] treewide: use configured value as the default color output Andrea Claudi
2023-09-14 15:30 ` [PATCH iproute2-next 0/2] configure: add support for color patchwork-bot+netdevbpf
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=20230915085912.78ffd25c@hermes.local \
--to=stephen@networkplumber.org \
--cc=aclaudi@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).