From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, thirteen, updated. ed62983f6240c89ad9f3f85cc7d8b136ea51ba8f
Date: Thu, 29 Nov 2012 16:46:37 +0100 [thread overview]
Message-ID: <20121129154646.EE52820259@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1630 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, thirteen has been updated
via ed62983f6240c89ad9f3f85cc7d8b136ea51ba8f (commit)
from 3b772d874a34a87798b1ae02ac0eeed3e3d5f60a (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 ed62983f6240c89ad9f3f85cc7d8b136ea51ba8f
Author: Arne Fitzenreiter <Arne_F(a)ipfire.org>
Date: Thu Nov 29 16:45:59 2012 +0100
compat-wireless: update to 3.6.8-1-snp.
-----------------------------------------------------------------------
Summary of changes:
lfs/compat-wireless | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/lfs/compat-wireless b/lfs/compat-wireless
index 6c6b791..8a3fd56 100644
--- a/lfs/compat-wireless
+++ b/lfs/compat-wireless
@@ -26,7 +26,7 @@ include Config
VERSUFIX=ipfire$(KCFG)
-VER = 3.6.6-1-snp
+VER = 3.6.8-1-snp
ifeq "$(KCFG)" "-xen"
KVER = 2.6.32.60
@@ -47,8 +47,7 @@ objects = $(DL_FILE) asix-4.4.0.tar.xz
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
asix-4.4.0.tar.xz = $(DL_FROM)/asix-4.4.0.tar.xz
-$(DL_FILE)_MD5 = e20f1b5a50095cf3483fd171ea9d3f92
-
+$(DL_FILE)_MD5 = 4120bc9841d6a1b5b92af34103f16a06
asix-4.4.0.tar.xz_MD5=633609e889de41554826e0e2cd7bffde
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-11-29 15:46 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=20121129154646.EE52820259@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