From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 3baefafee476f8f18ae36b6f8c59a70f399e0396
Date: Tue, 19 Apr 2022 09:45:53 +0000 [thread overview]
Message-ID: <4KjJp96ccfz2xc9@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2532 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 3baefafee476f8f18ae36b6f8c59a70f399e0396 (commit)
via 1a4e1bc3205d04fb94878696a3eadddf9a3a0ab6 (commit)
via 56fb66438d3c4d41d691c18e6ef55558708b3a9c (commit)
via 31592610cb7c26b2df56a3b82c14c9dba0ac19a9 (commit)
from 66ff5ffec85347f36abb7c173c66e8f9a23371b6 (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 3baefafee476f8f18ae36b6f8c59a70f399e0396
Merge: 66ff5ffec 1a4e1bc32
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Apr 19 09:45:39 2022 +0000
Merge branch 'next'
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/141 => core/167}/filelists/elinks | 0
config/rootfiles/{oldcore/66 => core/167}/filelists/pcmciautils | 0
config/rootfiles/{oldcore/125 => core/167}/filelists/xfsprogs | 0
3 files changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/141 => core/167}/filelists/elinks (100%)
copy config/rootfiles/{oldcore/66 => core/167}/filelists/pcmciautils (100%)
copy config/rootfiles/{oldcore/125 => core/167}/filelists/xfsprogs (100%)
Difference in files:
diff --git a/config/rootfiles/core/167/filelists/elinks b/config/rootfiles/core/167/filelists/elinks
new file mode 120000
index 000000000..10db4dd8f
--- /dev/null
+++ b/config/rootfiles/core/167/filelists/elinks
@@ -0,0 +1 @@
+../../../common/elinks
\ No newline at end of file
diff --git a/config/rootfiles/core/167/filelists/pcmciautils b/config/rootfiles/core/167/filelists/pcmciautils
new file mode 120000
index 000000000..7cbf8218c
--- /dev/null
+++ b/config/rootfiles/core/167/filelists/pcmciautils
@@ -0,0 +1 @@
+../../../common/pcmciautils
\ No newline at end of file
diff --git a/config/rootfiles/core/167/filelists/xfsprogs b/config/rootfiles/core/167/filelists/xfsprogs
new file mode 120000
index 000000000..91032964d
--- /dev/null
+++ b/config/rootfiles/core/167/filelists/xfsprogs
@@ -0,0 +1 @@
+../../../common/xfsprogs
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2022-04-19 9:45 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=4KjJp96ccfz2xc9@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