From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c5000130ec32c7fb07b54f41ca1d8af9a0b3209d
Date: Wed, 23 Jul 2014 20:57:42 +0200 [thread overview]
Message-ID: <20140723185742.EC09A21189@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1544 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 c5000130ec32c7fb07b54f41ca1d8af9a0b3209d (commit)
via ce12ce8cd7ebb3e190b84b9fc79c3d626f0c83d6 (commit)
from 9d9c825b4e2a58bbd9c7636d7eeb37a52f21d9c6 (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 c5000130ec32c7fb07b54f41ca1d8af9a0b3209d
Merge: 9d9c825 ce12ce8
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Jul 23 20:57:22 2014 +0200
Merge branch 'check_mk' of https://github.com/morlix/ipfire-2.x into next
commit ce12ce8cd7ebb3e190b84b9fc79c3d626f0c83d6
Author: Timo Eissler <timo(a)eissler.pro>
Date: Wed Jul 23 20:20:53 2014 +0200
check_mk: add backup config file
-----------------------------------------------------------------------
Summary of changes:
config/backup/includes/check_mk | 1 +
1 file changed, 1 insertion(+)
create mode 100644 config/backup/includes/check_mk
Difference in files:
diff --git a/config/backup/includes/check_mk b/config/backup/includes/check_mk
new file mode 100644
index 0000000..ca71046
--- /dev/null
+++ b/config/backup/includes/check_mk
@@ -0,0 +1 @@
+/etc/check_mk/
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-07-23 18:57 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=20140723185742.EC09A21189@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