From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core105, updated. 2d850c7944bf0fd7bfac91436151dcecafe3f623
Date: Fri, 23 Sep 2016 09:33:29 +0100 [thread overview]
Message-ID: <20160923083329.DEFDF1078E81@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1556 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, core105 has been updated
via 2d850c7944bf0fd7bfac91436151dcecafe3f623 (commit)
from e4ee7f0317547aacd36b9b5d31f9eb659ab5f455 (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 2d850c7944bf0fd7bfac91436151dcecafe3f623
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Sep 23 10:30:34 2016 +0200
core105: add openssl sse2 binaries
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/99 => core/105}/filelists/i586/openssl-sse2 | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/99 => core/105}/filelists/i586/openssl-sse2 (100%)
Difference in files:
diff --git a/config/rootfiles/core/105/filelists/i586/openssl-sse2 b/config/rootfiles/core/105/filelists/i586/openssl-sse2
new file mode 120000
index 0000000..f424713
--- /dev/null
+++ b/config/rootfiles/core/105/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:[~2016-09-23 8:33 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=20160923083329.DEFDF1078E81@git01.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