From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8bc689164ed8e1f2cab5e9690f78f0c744a7a5e2
Date: Sat, 05 Jul 2014 20:08:46 +0200 [thread overview]
Message-ID: <20140705180846.CE18121289@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1468 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 8bc689164ed8e1f2cab5e9690f78f0c744a7a5e2 (commit)
from 22ab0e0caee4613f0b821fc2e65e862c64e0a958 (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 8bc689164ed8e1f2cab5e9690f78f0c744a7a5e2
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Jul 5 20:08:28 2014 +0200
strongswan: Update to 5.2.0rc1.
-----------------------------------------------------------------------
Summary of changes:
lfs/strongswan | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/lfs/strongswan b/lfs/strongswan
index 7448c8d..a5bda74 100644
--- a/lfs/strongswan
+++ b/lfs/strongswan
@@ -24,7 +24,7 @@
include Config
-VER = 5.2.0dr6
+VER = 5.2.0rc1
THISAPP = strongswan-$(VER)
DL_FILE = $(THISAPP).tar.bz2
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 6b9ac43a3934dcdf66ccbdfebc54081b
+$(DL_FILE)_MD5 = ca260196e49ca5f15ff2507f20c4539a
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-07-05 18:08 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=20140705180846.CE18121289@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