From: "Markus Meier (maekke)" <maekke@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-cpp/muParser: ChangeLog muParser-1.32-r1.ebuild
Date: Mon, 26 Apr 2010 20:35:19 +0000 (UTC) [thread overview]
Message-ID: <20100426203520.32FB32C04C@corvid.gentoo.org> (raw)
maekke 10/04/26 20:35:19
Modified: ChangeLog muParser-1.32-r1.ebuild
Log:
amd64/x86 stable, bug #314045
(Portage version: 2.2_rc67/cvs/Linux x86_64)
Revision Changes Path
1.15 dev-cpp/muParser/ChangeLog
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-cpp/muParser/ChangeLog?rev=1.15&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-cpp/muParser/ChangeLog?rev=1.15&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-cpp/muParser/ChangeLog?r1=1.14&r2=1.15
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-cpp/muParser/ChangeLog,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- ChangeLog 20 Mar 2010 19:51:30 -0000 1.14
+++ ChangeLog 26 Apr 2010 20:35:19 -0000 1.15
@@ -1,6 +1,9 @@
# ChangeLog for dev-cpp/muParser
# Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-cpp/muParser/ChangeLog,v 1.14 2010/03/20 19:51:30 jlec Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-cpp/muParser/ChangeLog,v 1.15 2010/04/26 20:35:19 maekke Exp $
+
+ 26 Apr 2010; Markus Meier <maekke@gentoo.org> muParser-1.32-r1.ebuild:
+ amd64/x86 stable, bug #314045
*muParser-1.32-r1 (20 Mar 2010)
1.2 dev-cpp/muParser/muParser-1.32-r1.ebuild
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-cpp/muParser/muParser-1.32-r1.ebuild?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-cpp/muParser/muParser-1.32-r1.ebuild?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-cpp/muParser/muParser-1.32-r1.ebuild?r1=1.1&r2=1.2
Index: muParser-1.32-r1.ebuild
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-cpp/muParser/muParser-1.32-r1.ebuild,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- muParser-1.32-r1.ebuild 20 Mar 2010 19:51:30 -0000 1.1
+++ muParser-1.32-r1.ebuild 26 Apr 2010 20:35:19 -0000 1.2
@@ -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/dev-cpp/muParser/muParser-1.32-r1.ebuild,v 1.1 2010/03/20 19:51:30 jlec Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-cpp/muParser/muParser-1.32-r1.ebuild,v 1.2 2010/04/26 20:35:19 maekke Exp $
EAPI=2
inherit eutils
@@ -13,7 +13,7 @@
LICENSE="MIT"
SLOT="0"
-KEYWORDS="~amd64 ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos"
+KEYWORDS="amd64 ~ppc ~ppc64 x86 ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos"
IUSE="doc test"
RDEPEND=""
next reply other threads:[~2010-04-26 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 20:35 Markus Meier (maekke) [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-21 8:41 [gentoo-commits] gentoo-x86 commit in dev-cpp/muParser: ChangeLog muParser-1.32-r1.ebuild Justin Lecher (jlec)
2010-03-20 19:51 Justin Lecher (jlec)
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=20100426203520.32FB32C04C@corvid.gentoo.org \
--to=maekke@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