From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. ed971af3a411f8a1b54881fb16eaf97f3058623e
Date: Sun, 24 Feb 2019 16:39:03 +0000 [thread overview]
Message-ID: <20190224163903.D927884FDD4@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1557 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 ed971af3a411f8a1b54881fb16eaf97f3058623e (commit)
from 42e48984ad94fba114cde99a31efde63f2f42101 (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 ed971af3a411f8a1b54881fb16eaf97f3058623e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Feb 24 17:04:44 2019 +0100
core128: add sse2 openssl libs
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/100 => core/128}/filelists/i586/openssl-sse2 | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/100 => core/128}/filelists/i586/openssl-sse2 (100%)
Difference in files:
diff --git a/config/rootfiles/core/128/filelists/i586/openssl-sse2 b/config/rootfiles/core/128/filelists/i586/openssl-sse2
new file mode 120000
index 000000000..f424713d6
--- /dev/null
+++ b/config/rootfiles/core/128/filelists/i586/openssl-sse2
@@ -0,0 +1 @@
+../../../../common/i586/openssl-sse2
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-02-24 16:39 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=20190224163903.D927884FDD4@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