From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core92, updated. 72bdd1130c2b87f67f347800689f1a3f60e60b1e
Date: Tue, 14 Jul 2015 12:52:42 +0200 [thread overview]
Message-ID: <20150714105242.D6C6E2238E@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1486 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, core92 has been updated
via 72bdd1130c2b87f67f347800689f1a3f60e60b1e (commit)
from f0aa99fb7b03bb7ce6c7e5b65a864c877b586b93 (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 72bdd1130c2b87f67f347800689f1a3f60e60b1e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Jul 14 12:07:55 2015 +0200
core92: Ship SSE2 version of openssl
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/91 => core/92}/filelists/i586/openssl-sse2 | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/91 => core/92}/filelists/i586/openssl-sse2 (100%)
Difference in files:
diff --git a/config/rootfiles/core/92/filelists/i586/openssl-sse2 b/config/rootfiles/core/92/filelists/i586/openssl-sse2
new file mode 120000
index 0000000..f424713
--- /dev/null
+++ b/config/rootfiles/core/92/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:[~2015-07-14 10:52 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=20150714105242.D6C6E2238E@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