public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 025fb3b2d29b535bf6e5efd32732348b1ad0aecb
Date: Mon, 23 Sep 2024 14:39:57 +0000	[thread overview]
Message-ID: <4XC5Hd1ZVgz2xPF@people01.haj.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1503 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  025fb3b2d29b535bf6e5efd32732348b1ad0aecb (commit)
      from  009cd67f19c3620da6bc13bb5acb08bd87e5616b (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 025fb3b2d29b535bf6e5efd32732348b1ad0aecb
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Mon Sep 23 14:39:04 2024 +0000

    core189: Ship ntp because of OpenSSL mismatch warning
    
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/{oldcore/100 => core/189}/filelists/ntp | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 copy config/rootfiles/{oldcore/100 => core/189}/filelists/ntp (100%)

Difference in files:
diff --git a/config/rootfiles/core/189/filelists/ntp b/config/rootfiles/core/189/filelists/ntp
new file mode 120000
index 000000000..7542d86cb
--- /dev/null
+++ b/config/rootfiles/core/189/filelists/ntp
@@ -0,0 +1 @@
+../../../common/ntp
\ No newline at end of file


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2024-09-23 14: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=4XC5Hd1ZVgz2xPF@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