From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 0594323b79a4bf8ba390a4cd9a2c6833983174ac
Date: Fri, 24 Apr 2015 20:07:06 +0200 [thread overview]
Message-ID: <20150424180706.DA11721ACB@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1640 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 0594323b79a4bf8ba390a4cd9a2c6833983174ac (commit)
from f3c793854077e1368768af0137ffc1a885490381 (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 0594323b79a4bf8ba390a4cd9a2c6833983174ac
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Apr 24 20:06:13 2015 +0200
core90: remove missing file from openssl-0.9.8-files.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/90/filelists/openssl-0.9.8-files | 1 -
1 file changed, 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/90/filelists/openssl-0.9.8-files b/config/rootfiles/core/90/filelists/openssl-0.9.8-files
index cad5293..e80a57d 100644
--- a/config/rootfiles/core/90/filelists/openssl-0.9.8-files
+++ b/config/rootfiles/core/90/filelists/openssl-0.9.8-files
@@ -5,7 +5,6 @@ usr/lib/gnupg/gpgkeys_curl
usr/lib/apache/libphp5.so
usr/lib/squid/digest_ldap_auth
usr/lib/squid/basic_ldap_auth
-usr/lib/squid/digest_edirectory_auth
usr/lib/squid/ext_kerberos_ldap_group_acl
usr/lib/squid/ext_edirectory_userip_acl
usr/lib/squid/ext_ldap_group_acl
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-04-24 18:07 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=20150424180706.DA11721ACB@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