From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: netdev@vger.kernel.org, bwh@kernel.org
Cc: jesse.brandeburg@intel.com
Subject: ethtool: git tree not updated to v3.18
Date: Wed, 1 Apr 2015 14:30:06 -0700 [thread overview]
Message-ID: <20150401143006.000001f7@unknown> (raw)
Hi Ben,
When trying to check a bug just now I noticed that the master
branch of
git://git.kernel.org/pub/scm/network/ethtool/ethtool
still points to the v3.16 tag.
But kernel.org shows version 3.18 released. I did some quick
investigation and it looks like the v3.18 tag points to a dangling
commit that is not on a branch.
$ git log --graph --oneline v3.18 |head -n5
* ba9a11a Release version 3.18.
* 1e8811a Fix build with musl by using more common typedefs
* 99bc878 bug fix: SFP Tx BIAS uses memory wrong offset
* 4614098 Release version 3.16.
* 14ef76c test-cmdline: Disable test cases for --rxfh hash key parsing
$ git log --graph --oneline origin/master |head -n5
* 4614098 Release version 3.16.
* 14ef76c test-cmdline: Disable test cases for --rxfh hash key parsing
* 86c0326 ethtool: Support for configurable RSS hash key
* e633626 ethtool-copy.h: sync with net
* 05b8ad5 Release version 3.14.
Maybe you can merge the commits from your working branch back onto
master and make another 3.18.1 tag or something.
I just did:
git checkout master
git merge v3.18
which worked okay, I think.
next reply other threads:[~2015-04-01 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 21:30 Jesse Brandeburg [this message]
2015-04-02 9:50 ` ethtool: git tree not updated to v3.18 Daniel Borkmann
2015-04-02 18:23 ` Ben Hutchings
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=20150401143006.000001f7@unknown \
--to=jesse.brandeburg@intel.com \
--cc=bwh@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).