From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/symfony-event-dispatcher/
Date: Sun, 18 Dec 2016 23:18:06 +0000 (UTC) [thread overview]
Message-ID: <1482103047.1ebe4e80a1ec2c027eb0f2fc2eafc44fdbd3c83c.mjo@gentoo> (raw)
commit: 1ebe4e80a1ec2c027eb0f2fc2eafc44fdbd3c83c
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 18 23:11:16 2016 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sun Dec 18 23:17:27 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1ebe4e80
dev-php/symfony-event-dispatcher: add the PHP project as a co-maintainer.
Package-Manager: portage-2.3.0
dev-php/symfony-event-dispatcher/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/dev-php/symfony-event-dispatcher/metadata.xml b/dev-php/symfony-event-dispatcher/metadata.xml
index 5cce61f..2260041 100644
--- a/dev-php/symfony-event-dispatcher/metadata.xml
+++ b/dev-php/symfony-event-dispatcher/metadata.xml
@@ -9,6 +9,9 @@
<email>proxy-maint@gentoo.org</email>
<name>Proxy Maintainers</name>
</maintainer>
+ <maintainer type="project">
+ <email>php-bugs@gentoo.org</email>
+ </maintainer>
<longdescription>
The EventDispatcher component provides tools that allow your application components
to communicate with each other by dispatching events and listening to them.
next reply other threads:[~2016-12-18 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 23:18 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 17:42 [gentoo-commits] repo/gentoo:master commit in: dev-php/symfony-event-dispatcher/ Mart Raudsepp
2023-08-26 16:07 Andreas Sturmlechner
2021-05-10 6:58 Agostino Sarubbo
2021-05-06 6:55 Agostino Sarubbo
2020-08-18 22:34 Thomas Deutschmann
2019-07-18 13:01 Thomas Deutschmann
2017-11-14 14:47 Michael Orlitzky
2016-12-18 23:18 Michael Orlitzky
2016-12-18 23:18 Michael Orlitzky
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=1482103047.1ebe4e80a1ec2c027eb0f2fc2eafc44fdbd3c83c.mjo@gentoo \
--to=mjo@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