From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f89ab38d7936e1735e20df0873c9f5adf2398472
Date: Mon, 03 Jun 2013 17:55:13 +0200 [thread overview]
Message-ID: <20130603155513.E9A4D20595@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2208 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 f89ab38d7936e1735e20df0873c9f5adf2398472 (commit)
via e8676927f429f94197d8a4d8daff247de799b0b4 (commit)
via 7112943a8b72eb91a5954d4819850d0d15ced0ec (commit)
from 7f4f2f7d249ae2fc46ea513ff4f5a37b016e9ae3 (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 f89ab38d7936e1735e20df0873c9f5adf2398472
Author: Arne Fitzenreiter <Arne_F(a)ipfire.org>
Date: Mon Jun 3 17:54:01 2013 +0200
kernel: Updated to 3.2.46.
commit e8676927f429f94197d8a4d8daff247de799b0b4
Merge: 7112943 7f4f2f7
Author: Arne Fitzenreiter <Arne_F(a)ipfire.org>
Date: Mon Jun 3 14:49:29 2013 +0200
Merge branch 'next' of ssh://git.ipfire.org/pub/git/ipfire-2.x into next
commit 7112943a8b72eb91a5954d4819850d0d15ced0ec
Merge: 1bc8f87 79f9439
Author: Arne Fitzenreiter <Arne_F(a)ipfire.org>
Date: Thu May 16 21:47:33 2013 +0200
Merge remote-tracking branch 'ms/kernel-update' into next
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index 33474fb..a185431 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,7 +24,7 @@
include Config
-VER = 3.2.45
+VER = 3.2.46
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 = 817121285087d09c473a0aeb24a044e0
+$(DL_FILE)_MD5 = 8e2bf282b58b5ca0e2c9d5a1dbdbe193
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 966687ff27e450e04ff50e0da829dc00
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-06-03 15:55 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=20130603155513.E9A4D20595@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