From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. c253116d250aedcb9e340dc68cc52086700c698c
Date: Tue, 25 May 2021 11:50:10 +0000 [thread overview]
Message-ID: <4FqC7Q2hL5z2xMY@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1509 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 c253116d250aedcb9e340dc68cc52086700c698c (commit)
from 2b51f53cfd32d6f24aba49c8fde822be8bee6d56 (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 c253116d250aedcb9e340dc68cc52086700c698c
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue May 25 11:49:03 2021 +0000
core157: Ship python3-inotify
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/157/filelists/python3-inotify | 1 +
1 file changed, 1 insertion(+)
create mode 120000 config/rootfiles/core/157/filelists/python3-inotify
Difference in files:
diff --git a/config/rootfiles/core/157/filelists/python3-inotify b/config/rootfiles/core/157/filelists/python3-inotify
new file mode 120000
index 000000000..d2515bcba
--- /dev/null
+++ b/config/rootfiles/core/157/filelists/python3-inotify
@@ -0,0 +1 @@
+../../../common/python3-inotify
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-05-25 11:50 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=4FqC7Q2hL5z2xMY@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