From: "Christian Heim (phreak)" <phreak@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in dev-util/visual-regexp: metadata.xml ChangeLog
Date: Mon, 21 Apr 2008 17:27:38 +0000 [thread overview]
Message-ID: <E1Jnznm-00038O-S7@stork.gentoo.org> (raw)
phreak 08/04/21 17:27:38
Modified: metadata.xml ChangeLog
Log:
Fix up metadata.xml. If there's no maintainer for the package, the metadata also needs to contain m-needed@g.o.
(Portage version: 2.1.4.4)
Revision Changes Path
1.3 dev-util/visual-regexp/metadata.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/visual-regexp/metadata.xml?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/visual-regexp/metadata.xml?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/visual-regexp/metadata.xml?r1=1.2&r2=1.3
Index: metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-util/visual-regexp/metadata.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- metadata.xml 31 May 2007 02:15:30 -0000 1.2
+++ metadata.xml 21 Apr 2008 17:27:38 -0000 1.3
@@ -1,5 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
-<herd>no-herd</herd>
+ <herd>no-herd</herd>
+ <maintainer>
+ <email>maintainer-needed@gentoo.org</email>
+ <name>Default assignee for orphaned packages</name>
+ </maintainer>
</pkgmetadata>
1.8 dev-util/visual-regexp/ChangeLog
file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/visual-regexp/ChangeLog?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/visual-regexp/ChangeLog?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-util/visual-regexp/ChangeLog?r1=1.7&r2=1.8
Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/dev-util/visual-regexp/ChangeLog,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- ChangeLog 31 May 2007 02:15:30 -0000 1.7
+++ ChangeLog 21 Apr 2008 17:27:38 -0000 1.8
@@ -1,6 +1,10 @@
# ChangeLog for dev-util/visual-regexp
-# Copyright 2000-2007 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-util/visual-regexp/ChangeLog,v 1.7 2007/05/31 02:15:30 kloeri Exp $
+# Copyright 2000-2008 Gentoo Foundation; Distributed under the GPL v2
+# $Header: /var/cvsroot/gentoo-x86/dev-util/visual-regexp/ChangeLog,v 1.8 2008/04/21 17:27:38 phreak Exp $
+
+ 21 Apr 2008; Christian Heim <phreak@gentoo.org> metadata.xml:
+ Fix up metadata.xml. If there's no maintainer for the package, the metadata
+ also needs to contain m-needed@g.o.
31 May 2007; Bryan Østergaard <kloeri@gentoo.org> metadata.xml:
Remove myself as I'm retiring.
--
gentoo-commits@lists.gentoo.org mailing list
next reply other threads:[~2008-04-21 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 17:27 Christian Heim (phreak) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-23 8:15 [gentoo-commits] gentoo-x86 commit in dev-util/visual-regexp: metadata.xml ChangeLog Tom Wijsman (tomwij)
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=E1Jnznm-00038O-S7@stork.gentoo.org \
--to=phreak@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