From: Stefan Schmidt <stefan@osg.samsung.com>
To: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Cc: c.schoenert@t-online.de, pbrobinson@gmail.com
Subject: wpan-tools 0.6 release
Date: Wed, 23 Mar 2016 19:40:55 +0100 [thread overview]
Message-ID: <56F2E337.3040009@osg.samsung.com> (raw)
Hello.
It is a pleasure to announce the 0.6 release of wpan-tools.
Thanks to everyone who contributed!
0.6 is a bug fix release only. Some smaller things all over the place.
The important one is a fix to work with libnl >= 3.2.27 which is
getting picked up by more and more distributions.
Downloads and md5sums:
http://wpan.cakelab.org/releases/wpan-tools-0.6.tar.bz2
dd5367fe36ad8269263a29edad073bf7
http://wpan.cakelab.org/releases/wpan-tools-0.6.tar.gz
05322b1bc2fcdc040d326f0a5017aa4e
Carsten Schoenert (1):
iwpan: fix small typo, no functional change
Stefan Schmidt (18):
wpan-ping: align wpan-ping version with the general wpan-tools
version
wpan-ping: remove no longer used b option from getopt string
wpan-ping: fix usage message and mention -h option
wpan-ping: use correct define to fix getopt_long usage
wpan-ping: fix segfault for accessing invalid address
build: avoid redefinition errors with libnl >= 3.2.27
wpan-ping: remove unused struct sockaddr_nl variable
wpan-ping: check return value for setsockopt
wpan-ping: do not try to send data back to origin if we got an
error from recvfrom
wpan-ping: avoid leaking socket handle on error path
ci build: start to use Travis CI for continuous integration builds
ci build: add Coverity Scan service support to pur Travis config
wpan-ping: hide packet dump behind DEBUG flag
iwpan/wpan-ping: add some missing static attributes
wpan-ping: remove unused parameter from init_server()
wpan-ping: make sure we do not leak conf during wrong options exit
travis: add IRC notification of travis builds to linux-wpan channel
Release 0.6
regards
Stefan Schmidt
reply other threads:[~2016-03-23 18:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56F2E337.3040009@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=c.schoenert@t-online.de \
--cc=linux-wpan@vger.kernel.org \
--cc=pbrobinson@gmail.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.