From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 41e2c149a52c602ca1e5a7c9439e4e0d630620c0
Date: Sat, 08 Feb 2014 11:54:23 +0100 [thread overview]
Message-ID: <20140208105423.C623620C37@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1454 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 41e2c149a52c602ca1e5a7c9439e4e0d630620c0 (commit)
from 59b081c2a14a015fe47a5f32f169cf7b85fdca4b (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 41e2c149a52c602ca1e5a7c9439e4e0d630620c0
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Feb 8 11:54:00 2014 +0100
core76: remove hardcoded kernel version.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/76/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/76/update.sh b/config/rootfiles/core/76/update.sh
index c2a0d34..ba79d4b 100644
--- a/config/rootfiles/core/76/update.sh
+++ b/config/rootfiles/core/76/update.sh
@@ -71,7 +71,7 @@ esac
#
#
-KVER="3.10.28"
+KVER="xxxKVERxxx"
MOUNT=`grep "kernel" /boot/grub/grub.conf 2>/dev/null | tail -n 1 `
# Nur den letzten Parameter verwenden
echo $MOUNT > /dev/null
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-02-08 10:54 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=20140208105423.C623620C37@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