From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 69b2f2ab8e05bb1b4af5e97a62b4038cb764e795
Date: Tue, 22 Jan 2019 16:52:41 +0000 [thread overview]
Message-ID: <20190122165241.62A6084FDD4@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1486 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 3.x development tree".
The branch, master has been updated
via 69b2f2ab8e05bb1b4af5e97a62b4038cb764e795 (commit)
from 7403755a939d9315b9b0185229c9cd0110df9fb6 (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 69b2f2ab8e05bb1b4af5e97a62b4038cb764e795
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Jan 22 03:48:34 2019 +0000
strongswan: Update to 5.7.2
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
strongswan/strongswan.nm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/strongswan/strongswan.nm b/strongswan/strongswan.nm
index e3121e08f..bd5e696b0 100644
--- a/strongswan/strongswan.nm
+++ b/strongswan/strongswan.nm
@@ -4,7 +4,7 @@
###############################################################################
name = strongswan
-version = 5.7.1
+version = 5.7.2
release = 1
groups = Networking/VPN
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2019-01-22 16:52 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=20190122165241.62A6084FDD4@people01.i.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