From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 36ab906de4ff4edaf01e8d4f0e2909f0f325a769
Date: Wed, 28 Jun 2023 18:46:29 +0000 [thread overview]
Message-ID: <4QrrCB17phz2xZH@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1544 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, next has been updated
via 36ab906de4ff4edaf01e8d4f0e2909f0f325a769 (commit)
from 87d0d07bbca6c25e6458cc1cf8a513baf8fbc7fa (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 36ab906de4ff4edaf01e8d4f0e2909f0f325a769
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Jun 28 18:46:01 2023 +0000
core176: Re-ship libssh
This was also linked against OpenSSL 1.1.1.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/137 => core/176}/filelists/libssh | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/137 => core/176}/filelists/libssh (100%)
Difference in files:
diff --git a/config/rootfiles/core/176/filelists/libssh b/config/rootfiles/core/176/filelists/libssh
new file mode 120000
index 000000000..ecbb67053
--- /dev/null
+++ b/config/rootfiles/core/176/filelists/libssh
@@ -0,0 +1 @@
+../../../common/libssh
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-06-28 18:46 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=4QrrCB17phz2xZH@people01.haj.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