From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. d79fbce44e9baa9dceda2ad08bf91c16e04024d2
Date: Sun, 24 Aug 2014 15:22:26 +0200 [thread overview]
Message-ID: <20140824132226.AF340213C8@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1288 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 d79fbce44e9baa9dceda2ad08bf91c16e04024d2 (commit)
from ff6d34ab8b0cc8ad7f2c425bfc58f469aa6bb48e (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 d79fbce44e9baa9dceda2ad08bf91c16e04024d2
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Aug 24 15:22:04 2014 +0200
findutils: Cannot use exec here or the lockfile won't be removed
-----------------------------------------------------------------------
Summary of changes:
config/findutils/updatedb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/findutils/updatedb b/config/findutils/updatedb
index bc4809f..6cc1886 100644
--- a/config/findutils/updatedb
+++ b/config/findutils/updatedb
@@ -13,4 +13,4 @@ else
touch "$LOCKFILE"
fi
-exec /usr/bin/updatedb
+/usr/bin/updatedb
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-08-24 13:22 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=20140824132226.AF340213C8@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