From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] bridge-utils 1.6 release
Date: Mon, 17 Oct 2016 09:03:30 -0700 [thread overview]
Message-ID: <20161017090330.270fe160@xeon-e3> (raw)
Release of bridge-utils version 1.6
This is the first bridge-utils release in a long time.
There are not any new features, since bridge-utils is deprecated in
favor of bridge command in iproute2. But there are several small
bug fixes and minor cleanups.
Source:
http://www.kernel.org/pub/linux/utils/net/bridge-utils/bridge-utils.1.6.tar.gz
Repository:
git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/bridge-utils.git
Report problems (or enhancements) to the netdev@vger.kernel.org mailing list.
---
Andrey Mazo (4):
bridge-utils: Abort compilation on error in any subdirectory
bridge-utils: Remove unused variable in doc/Makefile.in
bridge-utils: AC_OUTPUT should be used without arguments
bridge-utils: Pretty print configure help
David Johnson (1):
bug with older glibc: "brctl show" shows nothing
Kylie McClain (1):
Fix building on musl libc
Russell Senior (1):
bridge-utils: Fix compile against linux-3.8.x
Stephen Hemminger (10):
Fix incorrect command in manual
Fix error message for incorrect command
Check error returns from write to sysfs
Fix typo's on man page
update email address
ignore build files
Clean up autoconf debris when doing make maintainer-clean
brctl: better error handling
man: add obsolete notice to man page
bridge-utils 1.6 release
Xiaochen Wang (1):
skip . and .. in accurately in isbridge()
Yegor Yefremov (1):
rename configure.in to configure.ac
next reply other threads:[~2016-10-17 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 16:03 Stephen Hemminger [this message]
2016-10-17 16:59 ` [ANNOUNCE] bridge-utils 1.6 release Alexander Alemayhu
2016-10-17 18:03 ` Rosen, Rami
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=20161017090330.270fe160@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).