public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brent Baude (ranger)" <ranger@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in kde-base/kgamma: kgamma-4.3.5.ebuild ChangeLog
Date: Thu, 11 Mar 2010 18:35:13 +0000	[thread overview]
Message-ID: <E1NpnE1-0002dJ-6u@stork.gentoo.org> (raw)

ranger      10/03/11 18:35:13

  Modified:             kgamma-4.3.5.ebuild ChangeLog
  Log:
  Marking kde-4.3.5 ppc for bug 300393
  (Portage version: 2.1.7.17/cvs/Linux ppc64)

Revision  Changes    Path
1.3                  kde-base/kgamma/kgamma-4.3.5.ebuild

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kgamma/kgamma-4.3.5.ebuild?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kgamma/kgamma-4.3.5.ebuild?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kgamma/kgamma-4.3.5.ebuild?r1=1.2&r2=1.3

Index: kgamma-4.3.5.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/kde-base/kgamma/kgamma-4.3.5.ebuild,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- kgamma-4.3.5.ebuild	20 Feb 2010 10:57:19 -0000	1.2
+++ kgamma-4.3.5.ebuild	11 Mar 2010 18:35:12 -0000	1.3
@@ -1,6 +1,6 @@
 # Copyright 1999-2010 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/kde-base/kgamma/kgamma-4.3.5.ebuild,v 1.2 2010/02/20 10:57:19 ssuominen Exp $
+# $Header: /var/cvsroot/gentoo-x86/kde-base/kgamma/kgamma-4.3.5.ebuild,v 1.3 2010/03/11 18:35:12 ranger Exp $
 
 EAPI="2"
 
@@ -8,7 +8,7 @@
 inherit kde4-meta
 
 DESCRIPTION="KDE screen gamma values kcontrol module"
-KEYWORDS="~alpha amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha amd64 ~hppa ~ia64 ppc ~ppc64 ~sparc x86 ~amd64-linux ~x86-linux"
 IUSE="debug +handbook"
 
 RDEPEND="



1.144                kde-base/kgamma/ChangeLog

file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kgamma/ChangeLog?rev=1.144&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kgamma/ChangeLog?rev=1.144&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kgamma/ChangeLog?r1=1.143&r2=1.144

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/kde-base/kgamma/ChangeLog,v
retrieving revision 1.143
retrieving revision 1.144
diff -u -r1.143 -r1.144
--- ChangeLog	2 Mar 2010 17:24:05 -0000	1.143
+++ ChangeLog	11 Mar 2010 18:35:12 -0000	1.144
@@ -1,6 +1,9 @@
 # ChangeLog for kde-base/kgamma
 # Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/kde-base/kgamma/ChangeLog,v 1.143 2010/03/02 17:24:05 tampakrap Exp $
+# $Header: /var/cvsroot/gentoo-x86/kde-base/kgamma/ChangeLog,v 1.144 2010/03/11 18:35:12 ranger Exp $
+
+  11 Mar 2010; Brent Baude <ranger@gentoo.org> kgamma-4.3.5.ebuild:
+  Marking kgamma-4.3.5 ppc stable for bug 300393
 
 *kgamma-4.4.1 (02 Mar 2010)
 






                 reply	other threads:[~2010-03-11 18:35 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=E1NpnE1-0002dJ-6u@stork.gentoo.org \
    --to=ranger@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