From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ad33c5fd5988835a5fe78bb2ce4cf5187c899e4d
Date: Sat, 11 Jan 2014 15:24:23 +0100 [thread overview]
Message-ID: <20140111142424.1298E211F2@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1478 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 ad33c5fd5988835a5fe78bb2ce4cf5187c899e4d (commit)
from 50da765d7ffd150cb6d3baf37dcdb956cd2b6c3a (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 ad33c5fd5988835a5fe78bb2ce4cf5187c899e4d
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Jan 11 15:24:02 2014 +0100
fifteen: add missing do.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/76/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/76/update.sh b/config/rootfiles/core/76/update.sh
index 5967212..f41f5f3 100644
--- a/config/rootfiles/core/76/update.sh
+++ b/config/rootfiles/core/76/update.sh
@@ -175,7 +175,7 @@ esac
rm -rf /srv/web/ipfire/html/themes/ipfire
# rename /etc/modprobe.d files
-for i in $(find /etc/modprobe.d/* | grep -v ".conf")
+for i in $(find /etc/modprobe.d/* | grep -v ".conf"); do
mv $i $i.conf
done
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-01-11 14:24 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=20140111142424.1298E211F2@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