public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-power/cpupower/
Date: Sun, 20 Sep 2015 16:10:31 +0000 (UTC)	[thread overview]
Message-ID: <1442765392.c65c54f053885e439bc7bff4c6a23c6d90c61f17.floppym@gentoo> (raw)

commit:     c65c54f053885e439bc7bff4c6a23c6d90c61f17
Author:     Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 20 16:09:16 2015 +0000
Commit:     Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Sun Sep 20 16:09:52 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c65c54f0

sys-power/cpupower: Add myself as a maintainer

Package-Manager: portage-2.2.20_p48

 sys-power/cpupower/metadata.xml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/sys-power/cpupower/metadata.xml b/sys-power/cpupower/metadata.xml
index 7c289c2..8278d75 100644
--- a/sys-power/cpupower/metadata.xml
+++ b/sys-power/cpupower/metadata.xml
@@ -6,6 +6,10 @@
 		<email>ssuominen@gentoo.org</email>
 		<name>Samuli Suominen</name>
 	</maintainer>
+	<maintainer>
+		<email>floppym@gentoo.org</email>
+		<name>Mike Gilbert</name>
+	</maintainer>
 	<use>
 		<flag name='cpufreq_bench'>Build and install the cpufreq_bench binary</flag>
 	</use>


             reply	other threads:[~2015-09-20 16:10 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20 16:10 Mike Gilbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-15 19:49 [gentoo-commits] repo/gentoo:master commit in: sys-power/cpupower/ Mike Gilbert
2024-08-15 16:37 Mike Gilbert
2024-08-15 16:37 Mike Gilbert
2024-04-24 17:59 Arthur Zamarin
2024-04-24 17:59 Arthur Zamarin
2024-04-24 17:42 Arthur Zamarin
2024-04-24 17:21 Arthur Zamarin
2024-04-24 17:14 Arthur Zamarin
2024-01-07  6:28 Sam James
2023-06-21  4:41 Arthur Zamarin
2023-06-03  4:00 Mike Gilbert
2023-06-03  3:59 Mike Gilbert
2023-06-01 20:16 Sam James
2023-06-01 20:12 Sam James
2023-06-01 20:12 Sam James
2023-06-01 20:04 Sam James
2022-06-03 18:56 Mike Gilbert
2022-06-03 18:56 Mike Gilbert
2022-01-10 23:00 Sam James
2022-01-09 20:08 Sam James
2022-01-09 20:08 Sam James
2022-01-09 10:25 Sam James
2021-08-27  1:48 Mike Gilbert
2021-01-03 19:40 Sam James
2021-01-03 19:40 Sam James
2020-12-06 20:50 Mike Gilbert
2020-12-06 20:48 Mike Gilbert
2020-02-01 18:01 Mike Gilbert
2019-11-25 22:10 Mike Gilbert
2019-11-25 22:10 Mike Gilbert
2019-10-05 18:56 Michał Górny
2017-12-21 21:16 Patrice Clement
2017-10-09 14:44 Sergei Trofimovich
2017-10-09 14:44 Sergei Trofimovich
2017-10-09 14:44 Sergei Trofimovich
2017-10-03 15:08 Sergei Trofimovich
2017-10-03 15:08 Sergei Trofimovich
2017-10-03  8:25 Sergei Trofimovich
2017-09-12 19:13 Mike Gilbert
2017-09-11  3:38 Mike Gilbert
2017-09-11  3:08 Mike Gilbert
2017-06-15  9:54 Agostino Sarubbo
2017-06-14  7:49 Agostino Sarubbo
2016-12-11 22:19 Mike Gilbert
2016-08-07  3:37 Mike Gilbert
2016-08-06 10:17 Pacho Ramos
2016-06-02 20:48 Mike Gilbert
2016-06-02 19:22 Mike Gilbert
2015-12-03 16:37 Mike Gilbert
2015-09-20 16:10 Mike Gilbert
2015-09-20  9:30 Agostino Sarubbo
2015-08-27  9:58 Agostino Sarubbo

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=1442765392.c65c54f053885e439bc7bff4c6a23c6d90c61f17.floppym@gentoo \
    --to=floppym@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