From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 4fbf276cae08c1e0b7cba0aba43c37c8e2151909
Date: Wed, 16 Apr 2014 07:24:11 +0200 [thread overview]
Message-ID: <20140416052412.11FDA20C48@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1652 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, master has been updated
via 4fbf276cae08c1e0b7cba0aba43c37c8e2151909 (commit)
from 2751238e6fc5ab0bfa01923cda24f7adc41b747f (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 4fbf276cae08c1e0b7cba0aba43c37c8e2151909
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Apr 16 06:52:01 2014 +0200
strongswan: rootfile update.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/strongswan | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/common/strongswan b/config/rootfiles/common/strongswan
index 9b61cd1..05ecef0 100644
--- a/config/rootfiles/common/strongswan
+++ b/config/rootfiles/common/strongswan
@@ -140,11 +140,11 @@ usr/libexec/ipsec/_copyright
usr/libexec/ipsec/_updown
usr/libexec/ipsec/_updown_espmark
usr/libexec/ipsec/charon
-usr/libexec/ipsec/openac
usr/libexec/ipsec/scepclient
usr/libexec/ipsec/starter
usr/libexec/ipsec/stroke
usr/sbin/ipsec
+#usr/share/man/man1/pki---acert.1
#usr/share/man/man1/pki---gen.1
#usr/share/man/man1/pki---issue.1
#usr/share/man/man1/pki---keyid.1
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-04-16 5:24 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=20140416052412.11FDA20C48@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