From: "Gysbert Wassenaar (nixnut)" <nixnut@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in games-board/crafty: crafty-22.1.ebuild ChangeLog
Date: Wed, 25 Jun 2008 19:12:04 +0000 [thread overview]
Message-ID: <E1KBaPU-0001zP-K0@stork.gentoo.org> (raw)
nixnut 08/06/25 19:12:04
Modified: crafty-22.1.ebuild ChangeLog
Log:
Stable on ppc wrt bug 229161
(Portage version: 2.1.4.4)
Revision Changes Path
1.4 games-board/crafty/crafty-22.1.ebuild
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/games-board/crafty/crafty-22.1.ebuild?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/games-board/crafty/crafty-22.1.ebuild?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/games-board/crafty/crafty-22.1.ebuild?r1=1.3&r2=1.4
Index: crafty-22.1.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/games-board/crafty/crafty-22.1.ebuild,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- crafty-22.1.ebuild 24 Jun 2008 16:06:54 -0000 1.3
+++ crafty-22.1.ebuild 25 Jun 2008 19:12:04 -0000 1.4
@@ -1,6 +1,6 @@
# Copyright 1999-2008 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/games-board/crafty/crafty-22.1.ebuild,v 1.3 2008/06/24 16:06:54 opfer Exp $
+# $Header: /var/cvsroot/gentoo-x86/games-board/crafty/crafty-22.1.ebuild,v 1.4 2008/06/25 19:12:04 nixnut Exp $
inherit flag-o-matic games
@@ -11,7 +11,7 @@
LICENSE="crafty"
SLOT="0"
-KEYWORDS="amd64 ~ppc x86"
+KEYWORDS="amd64 ppc x86"
IUSE="no-opts"
RESTRICT="test"
1.30 games-board/crafty/ChangeLog
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/games-board/crafty/ChangeLog?rev=1.30&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/games-board/crafty/ChangeLog?rev=1.30&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/games-board/crafty/ChangeLog?r1=1.29&r2=1.30
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/games-board/crafty/ChangeLog,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- ChangeLog 24 Jun 2008 16:06:54 -0000 1.29
+++ ChangeLog 25 Jun 2008 19:12:04 -0000 1.30
@@ -1,6 +1,9 @@
# ChangeLog for games-board/crafty
# Copyright 2002-2008 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/games-board/crafty/ChangeLog,v 1.29 2008/06/24 16:06:54 opfer Exp $
+# $Header: /var/cvsroot/gentoo-x86/games-board/crafty/ChangeLog,v 1.30 2008/06/25 19:12:04 nixnut Exp $
+
+ 25 Jun 2008; nixnut <nixnut@gentoo.org> crafty-22.1.ebuild:
+ Stable on ppc wrt bug 229161
24 Jun 2008; Christian Faulhammer <opfer@gentoo.org> crafty-22.1.ebuild:
stable x86, bug 229161
--
gentoo-commits@lists.gentoo.org mailing list
next reply other threads:[~2008-06-25 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 19:12 Gysbert Wassenaar (nixnut) [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-24 16:06 [gentoo-commits] gentoo-x86 commit in games-board/crafty: crafty-22.1.ebuild ChangeLog Christian Faulhammer (opfer)
2008-06-24 13:22 Thomas Anderson (gentoofan23)
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=E1KBaPU-0001zP-K0@stork.gentoo.org \
--to=nixnut@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