From: Stephen Hemminger <stephen@networkplumber.org>
To: nicolas.dichtel@6wind.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] iproute2 3.15.0 release
Date: Wed, 11 Jun 2014 09:07:37 -0700 [thread overview]
Message-ID: <20140611090737.5221c24c@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <53987CAD.2010306@6wind.com>
On Wed, 11 Jun 2014 17:58:37 +0200
Nicolas Dichtel <nicolas.dichtel@6wind.com> wrote:
> Le 11/06/2014 17:39, Stephen Hemminger a écrit :
> > On Wed, 11 Jun 2014 16:44:56 +0200
> > Nicolas Dichtel <nicolas.dichtel@6wind.com> wrote:
> >
> >> Le 10/06/2014 19:37, Stephen Hemminger a écrit :
> >>> Time for the release of iproute2 for 3.15
> >>>
> >>> The main new features are:
> >>> * ss gets more attention
> >>> * Support for HHF qdisc
> >>> * Updates to bridge command
> >>> * Lots of vxlan related changes
> >>> * Lots of little corrections and build fixes
> >>>
> >>> Source:
> >>> http://www.kernel.org/pub/linux/utils/net/iproute2/iproute2-3.15.0.tar.gz
> >>>
> >>> Repository:
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
> >> It seems that you have pushed the tag, but not the tagged commit
> >> (ce7aff3b8d0bb55321af2dbaa2f911319fdcc76b). In fact, I don't see the tag in the
> >> branch master.
> >
> > try now
> >
> Works, thank you.
> You gave a shortlog in the announcement, it is done between which tags?
> If I run 'git shortlog v3.14.0..v3.15.0', the output is shorter than yours.
Yes script does it but I think the merge branch from net-next confused
git shortlog.
prev parent reply other threads:[~2014-06-11 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 17:37 [ANNOUNCE] iproute2 3.15.0 release Stephen Hemminger
2014-06-11 14:44 ` Nicolas Dichtel
2014-06-11 15:39 ` Stephen Hemminger
2014-06-11 15:58 ` Nicolas Dichtel
2014-06-11 16:07 ` Stephen Hemminger [this message]
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=20140611090737.5221c24c@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.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).