From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b59da37ee2e5755c93645271ff810d284a014d35
Date: Mon, 04 May 2015 16:18:45 +0200 [thread overview]
Message-ID: <20150504141846.24A6C2230D@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1424 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 b59da37ee2e5755c93645271ff810d284a014d35 (commit)
from afa91a4df5755569b91c87a6b3b6fae095529ed1 (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 b59da37ee2e5755c93645271ff810d284a014d35
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon May 4 16:18:24 2015 +0200
core90: Ship updated fireinfo
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/87 => core/90}/filelists/fireinfo | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy config/rootfiles/{oldcore/87 => core/90}/filelists/fireinfo (100%)
Difference in files:
diff --git a/config/rootfiles/core/90/filelists/fireinfo b/config/rootfiles/core/90/filelists/fireinfo
new file mode 120000
index 0000000..c461155
--- /dev/null
+++ b/config/rootfiles/core/90/filelists/fireinfo
@@ -0,0 +1 @@
+../../../common/fireinfo
\ No newline at end of file
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-05-04 14:18 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=20150504141846.24A6C2230D@argus.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