From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 7de1da3fdfff84c75bba7bd9111fbbc72204995b
Date: Sat, 19 May 2012 11:22:45 +0200 [thread overview]
Message-ID: <20120519092253.BA85F200D5@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1502 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 7de1da3fdfff84c75bba7bd9111fbbc72204995b (commit)
from 5b6fdbf9d5cf00bcba7d78bfaa8dd976a5d96411 (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 7de1da3fdfff84c75bba7bd9111fbbc72204995b
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat May 19 11:22:18 2012 +0200
fireinfo: Update to 2.1.5.
Fixes issues on the Raspberry Pi Computer.
-----------------------------------------------------------------------
Summary of changes:
lfs/fireinfo | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/fireinfo b/lfs/fireinfo
index e0d83bf..f7fbbc4 100644
--- a/lfs/fireinfo
+++ b/lfs/fireinfo
@@ -24,7 +24,7 @@
include Config
-VER = 2.1.4
+VER = 2.1.5
THISAPP = fireinfo-v$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 4a5a027fadb7f81bda1224608a76c944
+$(DL_FILE)_MD5 = 7f5350212b6aff44cb361fcabdf991e0
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-05-19 9:22 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=20120519092253.BA85F200D5@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