From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 4c658a270eca30cc9b91dc639da5c69326013045
Date: Wed, 06 Aug 2014 18:05:55 +0200 [thread overview]
Message-ID: <20140806160556.65CF7215CD@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1460 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 4c658a270eca30cc9b91dc639da5c69326013045 (commit)
from 9188f6142c7681ad46cf9acbfc42c2780f951f6c (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 4c658a270eca30cc9b91dc639da5c69326013045
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Aug 6 18:05:14 2014 +0200
check_mk_agent: extract backup include before uninstall.
-----------------------------------------------------------------------
Summary of changes:
src/paks/check_mk_agent/uninstall.sh | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/src/paks/check_mk_agent/uninstall.sh b/src/paks/check_mk_agent/uninstall.sh
index 3a0860a..51449f5 100644
--- a/src/paks/check_mk_agent/uninstall.sh
+++ b/src/paks/check_mk_agent/uninstall.sh
@@ -22,6 +22,7 @@
############################################################################
#
. /opt/pakfire/lib/functions.sh
+extract_backup_includes
make_backup ${NAME}
remove_files
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-08-06 16:05 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=20140806160556.65CF7215CD@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