From: Andrea Claudi <aclaudi@redhat.com>
To: netdev@vger.kernel.org
Cc: Nikolay Aleksandrov <razor@blackwall.org>,
bridge@lists.linux-foundation.org,
David Ahern <dsahern@gmail.com>, Roopa Prabhu <roopa@nvidia.com>
Subject: [Bridge] [PATCH iproute2-next 0/2] configure: add support for color
Date: Wed, 13 Sep 2023 19:58:24 +0200 [thread overview]
Message-ID: <cover.1694625043.git.aclaudi@redhat.com> (raw)
This series add support for the color parameter in iproute2 configure
script. The idea is to make it possible for iproute2 users and packagers
to set a default value for the color option different from the current
one, COLOR_OPT_NEVER, while maintaining the current default behaviour.
Patch 1 add the color option to the configure script. Users can set
three different values, never, auto and always, with the same meanings
they have for the -c / -color ip option. Default value is 'never', which
results in ip, tc and bridge to maintain their current output behaviour
(i.e. colorless output).
Patch 2 makes it possible for ip, tc and bridge to use the configured
value for color as their default color output.
Andrea Claudi (2):
configure: add the --color option
treewide: use configured value as the default color output
Makefile | 3 ++-
bridge/bridge.c | 3 ++-
configure | 37 +++++++++++++++++++++++++++++++++++++
ip/ip.c | 2 +-
tc/tc.c | 2 +-
5 files changed, 43 insertions(+), 4 deletions(-)
--
2.41.0
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Claudi <aclaudi@redhat.com>
To: netdev@vger.kernel.org
Cc: Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
bridge@lists.linux-foundation.org,
Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>
Subject: [PATCH iproute2-next 0/2] configure: add support for color
Date: Wed, 13 Sep 2023 19:58:24 +0200 [thread overview]
Message-ID: <cover.1694625043.git.aclaudi@redhat.com> (raw)
This series add support for the color parameter in iproute2 configure
script. The idea is to make it possible for iproute2 users and packagers
to set a default value for the color option different from the current
one, COLOR_OPT_NEVER, while maintaining the current default behaviour.
Patch 1 add the color option to the configure script. Users can set
three different values, never, auto and always, with the same meanings
they have for the -c / -color ip option. Default value is 'never', which
results in ip, tc and bridge to maintain their current output behaviour
(i.e. colorless output).
Patch 2 makes it possible for ip, tc and bridge to use the configured
value for color as their default color output.
Andrea Claudi (2):
configure: add the --color option
treewide: use configured value as the default color output
Makefile | 3 ++-
bridge/bridge.c | 3 ++-
configure | 37 +++++++++++++++++++++++++++++++++++++
ip/ip.c | 2 +-
tc/tc.c | 2 +-
5 files changed, 43 insertions(+), 4 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-13 17:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 17:58 Andrea Claudi [this message]
2023-09-13 17:58 ` [PATCH iproute2-next 0/2] configure: add support for color Andrea Claudi
2023-09-13 17:58 ` [Bridge] [PATCH iproute2-next 1/2] configure: add the --color option Andrea Claudi
2023-09-13 17:58 ` Andrea Claudi
2023-09-15 15:59 ` [Bridge] " Stephen Hemminger
2023-09-15 15:59 ` Stephen Hemminger
2023-09-15 18:23 ` [Bridge] " David Ahern
2023-09-15 18:23 ` David Ahern
2023-09-15 19:52 ` [Bridge] " Andrea Claudi
2023-09-15 19:52 ` Andrea Claudi
2023-09-13 17:58 ` [Bridge] [PATCH iproute2-next 2/2] treewide: use configured value as the default color output Andrea Claudi
2023-09-13 17:58 ` Andrea Claudi
2023-09-14 15:30 ` [Bridge] [PATCH iproute2-next 0/2] configure: add support for color patchwork-bot+netdevbpf
2023-09-14 15:30 ` 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=cover.1694625043.git.aclaudi@redhat.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.