public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-libs/pagmo/
Date: Sat, 25 Jun 2011 17:22:08 +0000 (UTC)	[thread overview]
Message-ID: <ccf6670bc789cbb00969da63f1c1c3cfe75f652c.jlec@gentoo> (raw)

commit:     ccf6670bc789cbb00969da63f1c1c3cfe75f652c
Author:     Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 25 16:12:05 2011 +0000
Commit:     Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Sat Jun 25 16:12:05 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=ccf6670b

migrate from 'git' to 'git-2'

(Portage version: 2.2.0_alpha41/git/Linux x86_64, signed Manifest commit with key 70EB7916)

---
 sci-libs/pagmo/ChangeLog         |    3 +++
 sci-libs/pagmo/metadata.xml      |   16 ++++++++--------
 sci-libs/pagmo/pagmo-9999.ebuild |    2 +-
 3 files changed, 12 insertions(+), 9 deletions(-)

diff --git a/sci-libs/pagmo/ChangeLog b/sci-libs/pagmo/ChangeLog
index ce5b582..87b76c3 100644
--- a/sci-libs/pagmo/ChangeLog
+++ b/sci-libs/pagmo/ChangeLog
@@ -2,6 +2,9 @@
 # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
+  25 Jun 2011; Justin Lecher <jlec@gentoo.org> pagmo-9999.ebuild, metadata.xml:
+  migrate from 'git' to 'git-2'
+
   24 Jun 2011; Justin Lecher <jlec@gentoo.org> pagmo-9999.ebuild,
   +metadata.xml:
   metadata.xml added

diff --git a/sci-libs/pagmo/metadata.xml b/sci-libs/pagmo/metadata.xml
index 0bf16da..ce5ca8e 100644
--- a/sci-libs/pagmo/metadata.xml
+++ b/sci-libs/pagmo/metadata.xml
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
-  <herd>sci</herd>
-  <maintainer>
-    <email>sci@gentoo.org</email>
-  </maintainer>
-  <use>
-    <flag name="kepler">Automatically generated description for kepler</flag>
-    <flag name="nlopt">Automatically generated description for nlopt</flag>
-  </use>
+	<herd>sci</herd>
+	<maintainer>
+		<email>sci@gentoo.org</email>
+	</maintainer>
+	<use>
+		<flag name="kepler">Automatically generated description for kepler</flag>
+		<flag name="nlopt">Automatically generated description for nlopt</flag>
+	</use>
 </pkgmetadata>

diff --git a/sci-libs/pagmo/pagmo-9999.ebuild b/sci-libs/pagmo/pagmo-9999.ebuild
index 87c5298..cd1bca3 100644
--- a/sci-libs/pagmo/pagmo-9999.ebuild
+++ b/sci-libs/pagmo/pagmo-9999.ebuild
@@ -4,7 +4,7 @@
 
 EAPI=4
 
-inherit cmake-utils git
+inherit cmake-utils git-2
 
 DESCRIPTION="Parallelization engine for optimization problems"
 HOMEPAGE="http://pagmo.sourceforge.net/"



             reply	other threads:[~2011-06-25 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-25 17:22 Justin Lecher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-27 22:12 [gentoo-commits] proj/sci:master commit in: sci-libs/pagmo/ Horea Christian
2015-07-29  7:54 Justin Lecher
2015-07-23 21:06 Jauhien Piatlicki
2015-07-23 21:06 Jauhien Piatlicki
2014-01-06 18:33 Justin Lecher
2014-01-06 18:33 Justin Lecher
2011-06-24 17:09 Justin Lecher

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=ccf6670bc789cbb00969da63f1c1c3cfe75f652c.jlec@gentoo \
    --to=jlec@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