public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libaio/
Date: Sun, 22 May 2016 17:09:20 +0000 (UTC)	[thread overview]
Message-ID: <1463936858.0f272f5801dbbd1d9f2742e0d8d9ba9b5e96ffa0.gokturk@gentoo> (raw)

commit:     0f272f5801dbbd1d9f2742e0d8d9ba9b5e96ffa0
Author:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Thu May 19 04:24:34 2016 +0000
Commit:     Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Sun May 22 17:07:38 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0f272f58

dev-libs/libaio: update maintainer email and remove proxy-maint

Package-Manager: portage-2.2.28

 dev-libs/libaio/metadata.xml | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/dev-libs/libaio/metadata.xml b/dev-libs/libaio/metadata.xml
index 4e3baeb..9f4f6e4 100644
--- a/dev-libs/libaio/metadata.xml
+++ b/dev-libs/libaio/metadata.xml
@@ -2,12 +2,8 @@
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
   <maintainer type="person">
-    <email>gokturk@binghamton.edu</email>
-	<name>Göktürk Yüksek</name>
-  </maintainer>
-  <maintainer type="project">
-    <email>proxy-maint@gentoo.org</email>
-    <name>Proxy Maintainers</name>
+    <email>gokturk@gentoo.org</email>
+    <name>Göktürk Yüksek</name>
   </maintainer>
   <longdescription>Library to provide user-level kernel Asynchronous I/O (AIO)
  support for Linux (needs kernel patches as of 2.6.12)</longdescription>


             reply	other threads:[~2016-05-22 17:09 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-22 17:09 Göktürk Yüksek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-18  8:41 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libaio/ Arthur Zamarin
2025-10-01 20:08 Sam James
2025-10-01 20:02 Sam James
2025-10-01 20:02 Sam James
2025-09-07  2:18 Sam James
2025-08-26 11:43 Sam James
2025-05-30 16:12 Arthur Zamarin
2025-04-13 21:30 Sam James
2024-04-12  6:26 Arthur Zamarin
2024-04-12  6:26 Arthur Zamarin
2024-03-24 11:29 Sam James
2024-03-24 11:29 Sam James
2024-02-20  5:14 Sam James
2022-10-15  3:11 Sam James
2022-09-27  7:10 Agostino Sarubbo
2022-09-26  6:37 Arthur Zamarin
2022-09-26  6:24 Arthur Zamarin
2022-09-26  6:24 Arthur Zamarin
2022-09-25  7:28 Arthur Zamarin
2022-09-25  6:19 Agostino Sarubbo
2022-09-25  4:43 Sam James
2022-09-25  4:37 Sam James
2022-08-24  7:04 Sam James
2022-05-06  2:44 WANG Xuerui
2022-05-02  2:09 Sam James
2022-04-21 20:25 Sam James
2022-03-26  0:09 Sam James
2022-03-26  0:01 Sam James
2020-09-07  0:53 Sam James
2020-08-29 14:48 Thomas Deutschmann
2020-08-28 22:21 Sergei Trofimovich
2020-08-24 17:33 Sergei Trofimovich
2020-08-23  6:51 Sam James
2020-08-22  5:43 Agostino Sarubbo
2020-08-21 18:20 Agostino Sarubbo
2019-06-04  0:07 Thomas Deutschmann
2019-05-05 20:09 Mikle Kolyada
2019-04-24 22:54 Thomas Deutschmann
2019-04-24 22:39 Göktürk Yüksek
2017-02-23  2:30 Göktürk Yüksek
2016-04-23 18:13 Patrice Clement
2016-04-23  7:59 Patrice Clement

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=1463936858.0f272f5801dbbd1d9f2742e0d8d9ba9b5e96ffa0.gokturk@gentoo \
    --to=gokturk@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