public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ian Delaney (idella4)" <idella4@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-python/qserve: metadata.xml ChangeLog
Date: Tue, 13 Nov 2012 10:28:46 +0000 (UTC)	[thread overview]
Message-ID: <20121113102846.D54E820C65@flycatcher.gentoo.org> (raw)

idella4     12/11/13 10:28:46

  Modified:             metadata.xml ChangeLog
  Log:
  Updating maintainer, metadata.xml
  
  (Portage version: 2.1.11.30/cvs/Linux x86_64, unsigned Manifest commit)

Revision  Changes    Path
1.2                  dev-python/qserve/metadata.xml

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

Index: metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/qserve/metadata.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- metadata.xml	18 May 2012 11:39:35 -0000	1.1
+++ metadata.xml	13 Nov 2012 10:28:46 -0000	1.2
@@ -3,12 +3,7 @@
 <pkgmetadata>
 	<herd>python</herd>
 	<maintainer>
-		<email>tampakrap@gentoo.org</email>
-		<name>Theo Chatzimichos</name>
-		<description>Proxy maintainer. CC him on bugs</description>
-	</maintainer>
-	<maintainer>
-		<email>johneed@hotmail.com</email>
+		<email>idella4@gentoo.org</email>
 		<name>Ian Delaney</name>
 		<description>Maintainer. Assign bugs to him</description>
 	</maintainer>



1.3                  dev-python/qserve/ChangeLog

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

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-python/qserve/ChangeLog,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ChangeLog	30 Jul 2012 07:19:22 -0000	1.2
+++ ChangeLog	13 Nov 2012 10:28:46 -0000	1.3
@@ -1,6 +1,9 @@
 # ChangeLog for dev-python/qserve
 # Copyright 1999-2012 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-python/qserve/ChangeLog,v 1.2 2012/07/30 07:19:22 patrick Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-python/qserve/ChangeLog,v 1.3 2012/11/13 10:28:46 idella4 Exp $
+
+  14 Nov 2012; Ian Delaney <idella4@gentoo.org> metadata.xml:
+  Updating maintainer, metadata.xml
 
 *qserve-0.2.8 (30 Jul 2012)
 





             reply	other threads:[~2012-11-13 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 10:28 Ian Delaney (idella4) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-03 21:28 [gentoo-commits] gentoo-x86 commit in dev-python/qserve: metadata.xml ChangeLog Justin Lecher (jlec)
2015-06-07 15:49 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=20121113102846.D54E820C65@flycatcher.gentoo.org \
    --to=idella4@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