From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/gecode/
Date: Mon, 1 Aug 2016 13:15:33 +0000 (UTC) [thread overview]
Message-ID: <1470057276.a4c6aa1c4d788baf43d1b0f689d8f363dc56de04.mjo@gentoo> (raw)
commit: a4c6aa1c4d788baf43d1b0f689d8f363dc56de04
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 1 13:14:36 2016 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Mon Aug 1 13:14:36 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a4c6aa1c
dev-libs/gecode: fix metadata.xml schema.
In my recent addition of gecode-4.4.0, I made a copy/paste error and
duplicated the <use> element in metadata.xml. Michał's Travis CI
instance caught the error (thanks).
Package-Manager: portage-2.2.28
dev-libs/gecode/metadata.xml | 2 --
1 file changed, 2 deletions(-)
diff --git a/dev-libs/gecode/metadata.xml b/dev-libs/gecode/metadata.xml
index 8d55768..234da92 100644
--- a/dev-libs/gecode/metadata.xml
+++ b/dev-libs/gecode/metadata.xml
@@ -6,8 +6,6 @@
<flag name="gist">
Enable Gist, the Gecode Interactive Search Tool
</flag>
- </use>
- <use>
<flag name="gmp">
Enable trigonometric and transcendental float
constraints
next reply other threads:[~2016-08-01 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 13:15 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-12 23:31 [gentoo-commits] repo/gentoo:master commit in: dev-libs/gecode/ Andreas Sturmlechner
2018-01-12 22:49 Andreas Sturmlechner
2018-01-12 22:49 Andreas Sturmlechner
2017-08-05 13:53 Michael Orlitzky
2017-08-05 13:53 Michael Orlitzky
2017-05-06 22:20 David Seifert
2016-09-29 17:27 Michael Palimaka
2016-08-01 13:05 Michael Orlitzky
2016-08-01 12:50 Michael Orlitzky
2016-08-01 12:50 Michael Orlitzky
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=1470057276.a4c6aa1c4d788baf43d1b0f689d8f363dc56de04.mjo@gentoo \
--to=mjo@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