From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core128, updated. 1e1273df1d0baf60feb9931fe66e21eda014989c
Date: Sun, 24 Feb 2019 19:51:41 +0000 [thread overview]
Message-ID: <20190224195142.1B1DB84FDD4@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1555 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, core128 has been updated
via 1e1273df1d0baf60feb9931fe66e21eda014989c (commit)
from ed971af3a411f8a1b54881fb16eaf97f3058623e (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 1e1273df1d0baf60feb9931fe66e21eda014989c
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Feb 24 20:50:16 2019 +0100
core128: add openldap to update
openldap was linked against old openssl lib
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/66 => core/128}/filelists/openldap | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/66 => core/128}/filelists/openldap (100%)
Difference in files:
diff --git a/config/rootfiles/core/128/filelists/openldap b/config/rootfiles/core/128/filelists/openldap
new file mode 120000
index 000000000..80c324f76
--- /dev/null
+++ b/config/rootfiles/core/128/filelists/openldap
@@ -0,0 +1 @@
+../../../common/openldap
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-02-24 19:51 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=20190224195142.1B1DB84FDD4@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