From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 4d84d320a84591976f92a4ae343b8ffee26de6c7
Date: Sun, 07 Dec 2014 11:12:00 +0100 [thread overview]
Message-ID: <20141207101201.25AA521214@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 4d84d320a84591976f92a4ae343b8ffee26de6c7 (commit)
from e71475c13afeef652ae94a545978e354e21eb03e (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 4d84d320a84591976f92a4ae343b8ffee26de6c7
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Dec 7 11:11:41 2014 +0100
iw: update to 3.14.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/28 => core/86}/filelists/iw | 0
lfs/iw | 4 ++--
2 files changed, 2 insertions(+), 2 deletions(-)
copy config/rootfiles/{oldcore/28 => core/86}/filelists/iw (100%)
Difference in files:
diff --git a/config/rootfiles/core/86/filelists/iw b/config/rootfiles/core/86/filelists/iw
new file mode 120000
index 0000000..7c58a20
--- /dev/null
+++ b/config/rootfiles/core/86/filelists/iw
@@ -0,0 +1 @@
+../../../common/iw
\ No newline at end of file
diff --git a/lfs/iw b/lfs/iw
index e55bc5c..2d4ad34 100644
--- a/lfs/iw
+++ b/lfs/iw
@@ -24,7 +24,7 @@
include Config
-VER = 3.10
+VER = 3.14
THISAPP = iw-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 07219ad06535bc270f7a8873aba6d5fa
+$(DL_FILE)_MD5 = 66e41053f6fc0781b683b5b688442de6
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-12-07 10:12 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=20141207101201.25AA521214@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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