From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ddafd799cefa0fde02fd6ab08426485ec692afe7
Date: Sun, 30 Jun 2013 00:04:58 +0200 [thread overview]
Message-ID: <20130629220507.289A720621@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2084 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, next has been updated
via ddafd799cefa0fde02fd6ab08426485ec692afe7 (commit)
from f691d2ca97fe9db7a0d9fc465e896cfbdd139010 (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 ddafd799cefa0fde02fd6ab08426485ec692afe7
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Jun 30 00:04:32 2013 +0200
kernel: update to 3.2.48.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/70/update.sh | 2 +-
lfs/linux | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/70/update.sh b/config/rootfiles/core/70/update.sh
index 6fbbb48..4076f06 100644
--- a/config/rootfiles/core/70/update.sh
+++ b/config/rootfiles/core/70/update.sh
@@ -72,7 +72,7 @@ esac
#
#
-KVER="3.2.47"
+KVER="3.2.48"
MOUNT=`grep "kernel" /boot/grub/grub.conf 2>/dev/null | tail -n 1 `
# Nur den letzten Parameter verwenden
echo $MOUNT > /dev/null
diff --git a/lfs/linux b/lfs/linux
index d7fc6a2..f820dfb 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,7 +24,7 @@
include Config
-VER = 3.2.47
+VER = 3.2.48
RPI_PATCHES = linux-3.2.27-ada8b44
@@ -71,7 +71,7 @@ objects =$(DL_FILE) \
$(DL_FILE) = $(URL_IPFIRE)/$(DL_FILE)
rpi-patches-$(RPI_PATCHES).patch.xz = $(URL_IPFIRE)/rpi-patches-$(RPI_PATCHES).patch.xz
-$(DL_FILE)_MD5 = 2fc39387136006be982aac90daaa4e3a
+$(DL_FILE)_MD5 = f560aa5fcf07e57ea0ca66fdfdb53ef1
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 966687ff27e450e04ff50e0da829dc00
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-06-29 22:04 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=20130629220507.289A720621@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