From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/utfcpp/
Date: Sat, 29 Jan 2022 15:20:11 +0000 (UTC) [thread overview]
Message-ID: <1643469566.1da86064d1954b7024904c36c85a44bc55890c60.dlan@gentoo> (raw)
commit: 1da86064d1954b7024904c36c85a44bc55890c60
Author: Arfrever Frehtes Taifersar Arahesis <Arfrever <AT> Apache <DOT> Org>
AuthorDate: Mon Jan 24 03:00:00 2022 +0000
Commit: Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Sat Jan 29 15:19:26 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1da86064
dev-libs/utfcpp: Set CJK as co-maintainer.
Signed-off-by: Arfrever Frehtes Taifersar Arahesis <Arfrever <AT> Apache.Org>
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>
dev-libs/utfcpp/metadata.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/dev-libs/utfcpp/metadata.xml b/dev-libs/utfcpp/metadata.xml
index 3aee5d1f054e..b9907b54a199 100644
--- a/dev-libs/utfcpp/metadata.xml
+++ b/dev-libs/utfcpp/metadata.xml
@@ -5,9 +5,9 @@
<email>arfrever.fta@gmail.com</email>
<name>Arfrever Frehtes Taifersar Arahesis</name>
</maintainer>
- <maintainer type="person" proxied="proxy">
- <email>floppym@gentoo.org</email>
- <name>Mike Gilbert</name>
+ <maintainer type="project">
+ <email>cjk@gentoo.org</email>
+ <name>Cjk</name>
</maintainer>
<upstream>
<remote-id type="github">nemtrif/utfcpp</remote-id>
next reply other threads:[~2022-01-29 15:20 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 15:20 Yixun Lan [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-09 23:23 [gentoo-commits] repo/gentoo:master commit in: dev-libs/utfcpp/ Sam James
2025-03-09 23:23 Sam James
2025-03-09 22:58 Sam James
2025-03-09 22:55 Sam James
2025-03-09 22:55 Sam James
2025-03-09 22:55 Sam James
2025-03-09 22:55 Sam James
2024-12-28 0:05 Andreas Sturmlechner
2024-12-28 0:05 Andreas Sturmlechner
2024-03-07 23:46 Andreas Sturmlechner
2024-03-07 23:44 Andreas Sturmlechner
2024-02-28 15:23 Andreas Sturmlechner
2024-02-28 15:21 Andreas Sturmlechner
2023-09-27 16:44 WANG Xuerui
2022-08-18 2:53 Matt Turner
2022-07-29 8:01 Agostino Sarubbo
2022-07-29 7:59 Agostino Sarubbo
2022-07-28 23:06 Sam James
2022-07-28 7:06 Agostino Sarubbo
2022-07-28 6:30 Sam James
2022-07-28 6:30 Sam James
2022-07-28 6:30 Sam James
2022-03-09 8:59 Jakov Smolić
2022-02-28 7:06 Yixun Lan
2022-01-29 15:20 Yixun Lan
2022-01-29 15:20 Yixun Lan
2022-01-02 19:47 Arthur Zamarin
2022-01-02 19:07 Arthur Zamarin
2022-01-02 9:59 Sam James
2022-01-02 5:52 Sam James
2022-01-02 5:52 Sam James
2022-01-02 5:52 Sam James
2021-03-28 7:14 Sam James
2020-11-22 19:32 Mike Gilbert
2020-11-22 19:32 Mike Gilbert
2020-11-22 19:32 Mike Gilbert
2020-02-08 12:50 Sergei Trofimovich
2020-01-17 19:09 Mike Gilbert
2019-12-31 18:08 Aaron Bauman
2019-12-31 8:18 Agostino Sarubbo
2019-12-31 8:15 Agostino Sarubbo
2019-12-06 20:25 Mike Gilbert
2019-09-26 6:52 Sergei Trofimovich
2019-08-30 18:39 Sergei Trofimovich
2019-08-18 3:06 Aaron Bauman
2019-08-16 17:03 Mike Gilbert
2019-08-09 18:39 Mike Gilbert
2019-08-09 18:39 Mike Gilbert
2019-08-09 18:39 Mike Gilbert
2019-07-21 8:25 Sergei Trofimovich
2019-07-16 18:19 Andreas Sturmlechner
2019-02-17 17:40 Sergei Trofimovich
2016-08-07 8:02 Pacho Ramos
2016-01-15 9:03 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=1643469566.1da86064d1954b7024904c36c85a44bc55890c60.dlan@gentoo \
--to=dlan@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