From: "Jeff Horelick (jdhore)" <jdhore@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in app-arch/pigz: ChangeLog pigz-2.2.4.ebuild
Date: Mon, 30 Apr 2012 19:51:35 +0000 (UTC) [thread overview]
Message-ID: <20120430195135.12BB82004B@flycatcher.gentoo.org> (raw)
jdhore 12/04/30 19:51:35
Modified: ChangeLog pigz-2.2.4.ebuild
Log:
marked x86 per bug 402517
(Portage version: 2.2.0_alpha101/cvs/Linux i686)
Revision Changes Path
1.20 app-arch/pigz/ChangeLog
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-arch/pigz/ChangeLog?rev=1.20&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-arch/pigz/ChangeLog?rev=1.20&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-arch/pigz/ChangeLog?r1=1.19&r2=1.20
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-arch/pigz/ChangeLog,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- ChangeLog 30 Apr 2012 12:39:16 -0000 1.19
+++ ChangeLog 30 Apr 2012 19:51:34 -0000 1.20
@@ -1,6 +1,9 @@
# ChangeLog for app-arch/pigz
# Copyright 1999-2012 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/app-arch/pigz/ChangeLog,v 1.19 2012/04/30 12:39:16 ago Exp $
+# $Header: /var/cvsroot/gentoo-x86/app-arch/pigz/ChangeLog,v 1.20 2012/04/30 19:51:34 jdhore Exp $
+
+ 30 Apr 2012; Jeff Horelick <jdhore@gentoo.org> pigz-2.2.4.ebuild:
+ marked x86 per bug 402517
30 Apr 2012; Agostino Sarubbo <ago@gentoo.org> pigz-2.2.4.ebuild:
Stable for amd64, wrt bug #402517
1.3 app-arch/pigz/pigz-2.2.4.ebuild
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-arch/pigz/pigz-2.2.4.ebuild?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-arch/pigz/pigz-2.2.4.ebuild?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/app-arch/pigz/pigz-2.2.4.ebuild?r1=1.2&r2=1.3
Index: pigz-2.2.4.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/app-arch/pigz/pigz-2.2.4.ebuild,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- pigz-2.2.4.ebuild 30 Apr 2012 12:39:16 -0000 1.2
+++ pigz-2.2.4.ebuild 30 Apr 2012 19:51:34 -0000 1.3
@@ -1,6 +1,6 @@
# Copyright 1999-2012 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/app-arch/pigz/pigz-2.2.4.ebuild,v 1.2 2012/04/30 12:39:16 ago Exp $
+# $Header: /var/cvsroot/gentoo-x86/app-arch/pigz/pigz-2.2.4.ebuild,v 1.3 2012/04/30 19:51:34 jdhore Exp $
EAPI="4"
@@ -12,7 +12,7 @@
LICENSE="ZLIB"
SLOT="0"
-KEYWORDS="~alpha amd64 ~mips ~sparc ~x86 ~amd64-linux ~sparc64-solaris"
+KEYWORDS="~alpha amd64 ~mips ~sparc x86 ~amd64-linux ~sparc64-solaris"
IUSE="symlink test"
RDEPEND="sys-libs/zlib"
next reply other threads:[~2012-04-30 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 19:51 Jeff Horelick (jdhore) [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-03 13:47 [gentoo-commits] gentoo-x86 commit in app-arch/pigz: ChangeLog pigz-2.2.4.ebuild Sergey Popov (pinkbyte)
2012-04-30 12:39 Agostino Sarubbo (ago)
2012-03-26 5:44 Tim Harder (radhermit)
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=20120430195135.12BB82004B@flycatcher.gentoo.org \
--to=jdhore@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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