From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core114, updated. 2083519a64c82e8b68ef50cace6be56e7003aa3c
Date: Sun, 24 Sep 2017 14:09:43 +0100 [thread overview]
Message-ID: <20170924130944.0883E1081DE1@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1464 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, core114 has been updated
via 2083519a64c82e8b68ef50cace6be56e7003aa3c (commit)
from 3aa4579f8f7fddc46e60faf22f19228bf358d759 (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 2083519a64c82e8b68ef50cace6be56e7003aa3c
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Sep 24 13:35:01 2017 +0200
core114: add php to updater
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/111 => core/114}/filelists/php | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/111 => core/114}/filelists/php (100%)
Difference in files:
diff --git a/config/rootfiles/core/114/filelists/php b/config/rootfiles/core/114/filelists/php
new file mode 120000
index 0000000..1ae48d7
--- /dev/null
+++ b/config/rootfiles/core/114/filelists/php
@@ -0,0 +1 @@
+../../../common/php
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-09-24 13:09 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=20170924130944.0883E1081DE1@git01.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