public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/sysprof/
Date: Mon, 19 Feb 2018 20:03:35 +0000 (UTC)	[thread overview]
Message-ID: <1519070581.202b1bd62d6f72df222711fbd8e67673e95d1248.leio@gentoo> (raw)

commit:     202b1bd62d6f72df222711fbd8e67673e95d1248
Author:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 19 19:56:35 2018 +0000
Commit:     Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Mon Feb 19 20:03:01 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=202b1bd6

dev-util/sysprof: Switch maintenance to gnome@ as primary

sysprof is an optional dependency of gnome-builder and its previous
maintainers are all part of that. Given that gnome-builder is maintained
by gnome team, move sysprof to be maintained primarily by gnome@ as well.
Remove myself by name in the process, keep tetromino for now as he's not
me, and no need to remove at least an explicit CC unless he wants that.

Package-Manager: Portage-2.3.19, Repoman-2.3.6

 dev-util/sysprof/metadata.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/dev-util/sysprof/metadata.xml b/dev-util/sysprof/metadata.xml
index ea79c2ed134..2f805617ad1 100644
--- a/dev-util/sysprof/metadata.xml
+++ b/dev-util/sysprof/metadata.xml
@@ -1,14 +1,14 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
+<maintainer type="project">
+	<email>gnome@gentoo.org</email>
+	<name>Gentoo GNOME Desktop</name>
+</maintainer>
 <maintainer type="person">
 	<email>tetromino@gentoo.org</email>
 	<name>Alexandre Rostovtsev</name>
 </maintainer>
-<maintainer type="person">
-	<email>leio@gentoo.org</email>
-	<name>Mart Raudsepp</name>
-</maintainer>
 <longdescription lang="en">
 	Sysprof is a sampling CPU profiler for Linux that profiles the entire system,
 	not just a single application.


             reply	other threads:[~2018-02-19 20:03 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 20:03 Mart Raudsepp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-10  0:42 [gentoo-commits] repo/gentoo:master commit in: dev-util/sysprof/ Jakov Smolić
2024-11-09 10:40 Pacho Ramos
2023-05-03  6:33 Arthur Zamarin
2023-05-03  6:33 Arthur Zamarin
2023-03-18  2:28 Matt Turner
2022-10-30 15:42 Matt Turner
2022-09-24 20:05 Matt Turner
2022-03-25 18:25 Matt Turner
2021-12-19 16:59 Matt Turner
2021-07-17 23:14 Sam James
2021-06-13 20:25 Sam James
2021-06-07  1:06 Matt Turner
2021-02-17 18:42 Sam James
2021-02-17 14:21 Sam James
2020-12-04  1:32 Matt Turner
2020-12-04  1:32 Matt Turner
2020-07-04 12:00 Mart Raudsepp
2020-03-02 19:23 Mart Raudsepp
2020-03-01 16:18 Mart Raudsepp
2019-12-23 21:26 Mart Raudsepp
2019-07-27  8:36 Mart Raudsepp
2019-05-18 19:59 Mart Raudsepp
2018-12-17 15:08 Mart Raudsepp
2018-08-02 20:58 Mart Raudsepp
2018-02-19 20:03 Mart Raudsepp
2018-02-06 18:36 Thomas Deutschmann
2018-01-26 15:03 Mikle Kolyada
2017-06-05  0:13 Mart Raudsepp
2017-06-05  0:13 Mart Raudsepp
2017-06-05  0:13 Mart Raudsepp
2017-04-18 11:14 Mart Raudsepp
2016-11-12 12:23 Gilles Dartiguelongue

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=1519070581.202b1bd62d6f72df222711fbd8e67673e95d1248.leio@gentoo \
    --to=leio@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