From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Minor update to bridge-utils
Date: Thu, 4 Mar 2021 09:34:46 -0800 [thread overview]
Message-ID: <20210304093446.356ba862@hermes.local> (raw)
Small changes to bridge-utils to address some minor issues.
1. The default branch is main not master
2. Fixed some compiler warnings because Gcc 10 and Clang now
do checks for string overflow.
3. Made a backup repository mirror at github.
4. Fixed version string printed
This is not a required update, none of these are important
or critical to users.
Do not intend to do any new features or serious fixes to
bridge-utils; all users should convert to iproute2/bridge command.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: [Bridge] Minor update to bridge-utils
Date: Thu, 4 Mar 2021 09:34:46 -0800 [thread overview]
Message-ID: <20210304093446.356ba862@hermes.local> (raw)
Small changes to bridge-utils to address some minor issues.
1. The default branch is main not master
2. Fixed some compiler warnings because Gcc 10 and Clang now
do checks for string overflow.
3. Made a backup repository mirror at github.
4. Fixed version string printed
This is not a required update, none of these are important
or critical to users.
Do not intend to do any new features or serious fixes to
bridge-utils; all users should convert to iproute2/bridge command.
next reply other threads:[~2021-03-04 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 17:34 Stephen Hemminger [this message]
2021-03-04 17:34 ` [Bridge] Minor update to bridge-utils Stephen Hemminger
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=20210304093446.356ba862@hermes.local \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--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.