From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 170769d4b46748a196c114c697a2f4a066f088ff
Date: Sun, 24 Jun 2012 16:18:16 +0200 [thread overview]
Message-ID: <20120624141816.DECC4200A3@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1483 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 3.x development tree".
The branch, master has been updated
via 170769d4b46748a196c114c697a2f4a066f088ff (commit)
from 4e8b2c0697da6c0a96e7d4559a97315883f6c516 (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 170769d4b46748a196c114c697a2f4a066f088ff
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Jun 24 16:18:05 2012 +0200
kmod: Disable testsuite (again).
-----------------------------------------------------------------------
Summary of changes:
kmod/kmod.nm | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
Difference in files:
diff --git a/kmod/kmod.nm b/kmod/kmod.nm
index de953e9..3c80b72 100644
--- a/kmod/kmod.nm
+++ b/kmod/kmod.nm
@@ -5,7 +5,7 @@
name = kmod
version = 9
-release = 1
+release = 2
maintainer = Michael Tremer <michael.tremer(a)ipfire.org>
groups = System/Kernel
@@ -33,9 +33,7 @@ build
--with-xz \
--with-zlib
- test
- make check
- end
+ # The testsuite does generate lots of errors.
install_cmds
mkdir -pv %{BUILDROOT}%{prefix}/lib/modprobe.d
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2012-06-24 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=20120624141816.DECC4200A3@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