From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 6003c4bbdb46094dcbcf63939395fe3bda82da70
Date: Tue, 03 Dec 2013 14:00:51 +0100 [thread overview]
Message-ID: <20131203130051.3118D2155D@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 6003c4bbdb46094dcbcf63939395fe3bda82da70 (commit)
from 4ea955c544fa5ff4939449bc163426fc36e1482f (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 6003c4bbdb46094dcbcf63939395fe3bda82da70
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Oct 24 19:41:17 2013 +0200
strongswan: Rootfile update.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/strongswan | 1 -
1 file changed, 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/strongswan b/config/rootfiles/common/strongswan
index d045c31..732e327 100644
--- a/config/rootfiles/common/strongswan
+++ b/config/rootfiles/common/strongswan
@@ -87,7 +87,6 @@ usr/libexec/ipsec/_updown
usr/libexec/ipsec/_updown_espmark
usr/libexec/ipsec/charon
usr/libexec/ipsec/openac
-usr/libexec/ipsec/pki
usr/libexec/ipsec/scepclient
usr/libexec/ipsec/starter
usr/libexec/ipsec/stroke
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-12-03 13:00 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=20131203130051.3118D2155D@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