From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core127, updated. f8d407e5f7ff0812beaa6b45eae18b57475aa3d8
Date: Tue, 29 Jan 2019 21:36:55 +0000 [thread overview]
Message-ID: <20190129213655.A4D6D84FDD4@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1618 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, core127 has been updated
via f8d407e5f7ff0812beaa6b45eae18b57475aa3d8 (commit)
from d78ef9851d0591aff04228e05296f91f997ba7ab (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 f8d407e5f7ff0812beaa6b45eae18b57475aa3d8
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Jan 29 22:36:01 2019 +0100
core127: add openssl-sse2 libs to i586 updater
this file was missing in core126
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/100 => core/127}/filelists/i586/openssl-sse2 | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/100 => core/127}/filelists/i586/openssl-sse2 (100%)
Difference in files:
diff --git a/config/rootfiles/core/127/filelists/i586/openssl-sse2 b/config/rootfiles/core/127/filelists/i586/openssl-sse2
new file mode 120000
index 000000000..f424713d6
--- /dev/null
+++ b/config/rootfiles/core/127/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-01-29 21:36 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=20190129213655.A4D6D84FDD4@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