From: "Patrice Clement" <monsieurp@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/uchardet/
Date: Sat, 5 Mar 2016 11:39:26 +0000 (UTC) [thread overview]
Message-ID: <1457106996.c3bf79a9a64da5be7ed9a6343e18f141cabc72bd.monsieurp@gentoo> (raw)
commit: c3bf79a9a64da5be7ed9a6343e18f141cabc72bd
Author: Ilya Tumaykin <itumaykin <AT> gmail <DOT> com>
AuthorDate: Fri Mar 4 14:47:50 2016 +0000
Commit: Patrice Clement <monsieurp <AT> gentoo <DOT> org>
CommitDate: Fri Mar 4 15:56:36 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c3bf79a9
dev-libs/uchardet: remove obsolete maintainer description from metadata
I'm the only maintainer. It's obvious who should be assignee in bugs.
Package-Manager: portage-2.2.27
dev-libs/uchardet/metadata.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/dev-libs/uchardet/metadata.xml b/dev-libs/uchardet/metadata.xml
index 3fc943d..97c636b 100644
--- a/dev-libs/uchardet/metadata.xml
+++ b/dev-libs/uchardet/metadata.xml
@@ -4,7 +4,6 @@
<maintainer type="person">
<email>itumaykin+gentoo@gmail.com</email>
<name>Coacher</name>
- <description>Proxied maintainer; set to assignee in all bugs</description>
</maintainer>
<maintainer type="project">
<email>proxy-maint@gentoo.org</email>
next reply other threads:[~2016-03-06 11:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 11:39 Patrice Clement [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-03 23:07 [gentoo-commits] repo/gentoo:master commit in: dev-libs/uchardet/ Patrice Clement
2016-10-01 12:05 Jeroen Roovers
2016-07-21 14:53 Göktürk Yüksek
2016-07-21 14:53 Göktürk Yüksek
2016-07-07 11:15 Tobias Klausmann
2016-06-08 12:46 Patrice Clement
2016-06-07 12:40 Tobias Klausmann
2016-05-10 9:28 Ian Delaney
2016-05-10 9:28 Ian Delaney
2016-03-14 22:12 Agostino Sarubbo
2016-02-25 17:19 Markus Meier
2016-02-06 8:37 Jeroen Roovers
2016-02-05 7:46 Ian Delaney
2016-02-02 8:48 Ian Delaney
2016-01-25 9:46 Patrice Clement
2016-01-25 9:22 Ian Delaney
2015-09-01 19:19 Tobias Klausmann
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=1457106996.c3bf79a9a64da5be7ed9a6343e18f141cabc72bd.monsieurp@gentoo \
--to=monsieurp@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