From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: compat-wireless-2.6.37-3-sn contains wrong files
Date: Sat, 08 Jan 2011 23:46:35 +0100 [thread overview]
Message-ID: <4D28E94B.1010806@hauke-m.de> (raw)
plusquezero on IRC complained about compat-wireless-2.6.37-3-sn not
compiling on his system with kernel 2.6.32 (
http://pastebin.com/bKyZpKSr ). I tried to create such a release and had
no problems, but the released tar balls at
http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.37/ are
containing some extra files. These files are available in
compat-wireless based on linux-next but not in the version based on
2.6.27. Something in the script creating this release went wrong.
Attached is the diffstat beetween compat-wireless-2.6.37-3-sn.tar.bz2
and the version I generated myself with "./scripts/admin-refresh.sh -s
-n" from the git branch remotes/origin/linux-2.6.37.y of
compat-wireless.git and compat.git.
Hauke
hauke@hauke:~/compat-wireless/compat-wireless-2.6.37-3-sn$ diff -Naurx
.git -x pending-stable -x tmp.patch -x build.sh -x compiletest.sh -x
scripts . ../compat-wireless-git |diffstat
code-metrics.txt | 12
compat/compat-2.6.38.c | 50 --
compat/kfifo.c | 608 ------------------------------
compat_base_tree | 2
include/linux/average.h | 5
include/linux/kfifo.h | 857
-------------------------------------------
include/linux/rfkill.h | 32 -
include/net/bluetooth/mgmt.h | 87 ----
net/bluetooth/mgmt.c | 308 ---------------
net/wireless/mesh.c | 142 -------
10 files changed, 7 insertions(+), 2096 deletions(-)
next reply other threads:[~2011-01-08 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 22:46 Hauke Mehrtens [this message]
2011-01-13 0:43 ` compat-wireless-2.6.37-3-sn contains wrong files Luis R. Rodriguez
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=4D28E94B.1010806@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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 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).