From: "Peter Müller" <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 672582488b302da48c35e0652dd8609f5954d8e2
Date: Tue, 10 May 2022 13:54:48 +0000 [thread overview]
Message-ID: <4KyKKh4FdYz2xjD@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1483 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 672582488b302da48c35e0652dd8609f5954d8e2 (commit)
from 0e48c84c42407fc326bafba6c6166a38a0c3a3a4 (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 672582488b302da48c35e0652dd8609f5954d8e2
Author: Peter Müller <peter.mueller(a)ipfire.org>
Date: Tue May 10 13:54:25 2022 +0000
Core Update 168: Ship GnuPG
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/106 => core/168}/filelists/gnupg | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/106 => core/168}/filelists/gnupg (100%)
Difference in files:
diff --git a/config/rootfiles/core/168/filelists/gnupg b/config/rootfiles/core/168/filelists/gnupg
new file mode 120000
index 000000000..a1a156447
--- /dev/null
+++ b/config/rootfiles/core/168/filelists/gnupg
@@ -0,0 +1 @@
+../../../common/gnupg
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-05-10 13:54 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=4KyKKh4FdYz2xjD@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