public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher (jlec)" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-python/rackspace-monitoring: metadata.xml ChangeLog
Date: Wed,  3 Jun 2015 21:29:22 +0000 (UTC)	[thread overview]
Message-ID: <20150603212922.CD567A1C@oystercatcher.gentoo.org> (raw)

jlec        15/06/03 21:29:22

  Modified:             metadata.xml ChangeLog
  Log:
  Add pypi to remote-id in metadata.xml
  
  (Portage version: 2.2.20/cvs/Linux x86_64, signed Manifest commit with key E9402A79B03529A2!)

Revision  Changes    Path
1.2                  dev-python/rackspace-monitoring/metadata.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/rackspace-monitoring/metadata.xml?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/rackspace-monitoring/metadata.xml?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/rackspace-monitoring/metadata.xml?r1=1.1&r2=1.2

Index: metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/rackspace-monitoring/metadata.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- metadata.xml	8 Feb 2014 01:13:13 -0000	1.1
+++ metadata.xml	3 Jun 2015 21:29:22 -0000	1.2
@@ -9,5 +9,7 @@
   <longdescription lang="en">
     Client library for Rackspace Cloud Monitoring.
   </longdescription>
+  <upstream>
+    <remote-id type="pypi">rackspace-monitoring</remote-id>
+  </upstream>
 </pkgmetadata>
-



1.6                  dev-python/rackspace-monitoring/ChangeLog

file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/rackspace-monitoring/ChangeLog?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/rackspace-monitoring/ChangeLog?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-python/rackspace-monitoring/ChangeLog?r1=1.5&r2=1.6

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/rackspace-monitoring/ChangeLog,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- ChangeLog	14 Jan 2015 01:52:05 -0000	1.5
+++ ChangeLog	3 Jun 2015 21:29:22 -0000	1.6
@@ -1,6 +1,9 @@
 # ChangeLog for dev-python/rackspace-monitoring
 # Copyright 1999-2015 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-python/rackspace-monitoring/ChangeLog,v 1.5 2015/01/14 01:52:05 prometheanfire Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-python/rackspace-monitoring/ChangeLog,v 1.6 2015/06/03 21:29:22 jlec Exp $
+
+  03 Jun 2015; Justin Lecher <jlec@gentoo.org> metadata.xml:
+  Add pypi to remote-id in metadata.xml
 
 *rackspace-monitoring-0.6.5 (14 Jan 2015)
 





             reply	other threads:[~2015-06-03 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 21:29 Justin Lecher (jlec) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-07 15:50 [gentoo-commits] gentoo-x86 commit in dev-python/rackspace-monitoring: metadata.xml ChangeLog 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=20150603212922.CD567A1C@oystercatcher.gentoo.org \
    --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