From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. c218306799f90a22725c0bd76bcee974003c19e3
Date: Sun, 05 Apr 2015 19:46:12 +0200 [thread overview]
Message-ID: <20150405174613.53C6D21AD1@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1628 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 c218306799f90a22725c0bd76bcee974003c19e3 (commit)
from a40c4c4374f479feed02082487dde674d06d7a24 (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 c218306799f90a22725c0bd76bcee974003c19e3
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Sat Apr 4 22:29:29 2015 +0200
pigz: Update to 2.3.3.
Also enable testsuite.
Fixes #10728.
-----------------------------------------------------------------------
Summary of changes:
pigz/pigz.nm | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/pigz/pigz.nm b/pigz/pigz.nm
index 27a30a2..bb8eab3 100644
--- a/pigz/pigz.nm
+++ b/pigz/pigz.nm
@@ -4,7 +4,7 @@
###############################################################################
name = pigz
-version = 2.2.5
+version = 2.3.3
release = 1
groups = Applications/Compression
@@ -28,6 +28,10 @@ build
make_build_targets += CFLAGS="%{CFLAGS}"
+ test
+ make test
+ end
+
install
install -p -D pigz %{BUILDROOT}%{bindir}/pigz
ln -svf pigz %{BUILDROOT}%{bindir}/unpigz
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2015-04-05 17:46 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=20150405174613.53C6D21AD1@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