From: "Matthew Smith" <matthew@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-proxy/mitmproxy/
Date: Thu, 7 Dec 2023 16:22:01 +0000 (UTC) [thread overview]
Message-ID: <1701965769.c3d7778b6fdc3cb68163d8f65233b424f859b626.matthew@gentoo> (raw)
commit: c3d7778b6fdc3cb68163d8f65233b424f859b626
Author: Matthew Smith <matthew <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 7 16:16:09 2023 +0000
Commit: Matthew Smith <matthew <AT> gentoo <DOT> org>
CommitDate: Thu Dec 7 16:16:09 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c3d7778b
net-proxy/mitmproxy: drop myself as a maintainer
Signed-off-by: Matthew Smith <matthew <AT> gentoo.org>
net-proxy/mitmproxy/metadata.xml | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/net-proxy/mitmproxy/metadata.xml b/net-proxy/mitmproxy/metadata.xml
index 876ef79751b4..33bee145a3c4 100644
--- a/net-proxy/mitmproxy/metadata.xml
+++ b/net-proxy/mitmproxy/metadata.xml
@@ -1,10 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>matthew@gentoo.org</email>
- <name>Matthew Smith</name>
- </maintainer>
+ <!-- maintainer-needed -->
<longdescription lang="en">
mitmproxy is your swiss-army knife for debugging,
testing, privacy measurements, and penetration
next reply other threads:[~2023-12-07 16:22 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 16:22 Matthew Smith [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-07 2:07 [gentoo-commits] repo/gentoo:master commit in: net-proxy/mitmproxy/ Michał Górny
2025-04-30 5:36 Michał Górny
2025-04-20 11:43 Michał Górny
2025-01-25 11:01 Arthur Zamarin
2025-01-04 16:17 Sam James
2024-12-31 16:01 Michał Górny
2024-12-31 16:01 Michał Górny
2023-03-06 16:23 Arthur Zamarin
2023-02-21 10:00 Michał Górny
2023-02-21 9:30 Sam James
2022-12-05 20:17 Arthur Zamarin
2022-11-18 8:49 Arthur Zamarin
2022-11-02 12:31 Matthew Smith
2022-09-09 9:48 Matthew Smith
2022-08-17 7:06 Agostino Sarubbo
2022-07-10 8:40 Matthew Smith
2022-07-10 8:40 Matthew Smith
2022-07-10 6:17 Agostino Sarubbo
2022-05-21 8:17 Matthew Smith
2022-05-14 10:05 Matthew Smith
2022-04-28 17:37 Matthew Smith
2022-02-13 19:06 Matthew Smith
2022-01-21 7:08 Joonas Niilola
2021-12-04 9:45 Joonas Niilola
2021-10-31 3:00 Sam James
2021-09-17 18:19 John Helmert III
2021-09-17 9:18 Agostino Sarubbo
2021-09-16 20:23 Ionen Wolkens
2021-09-16 18:44 Ionen Wolkens
2021-09-11 8:18 Joonas Niilola
2021-08-19 1:25 Agostino Sarubbo
2021-08-07 9:08 Ionen Wolkens
2021-07-19 10:09 Ionen Wolkens
2021-05-02 12:37 Mikle Kolyada
2021-03-01 9:20 Agostino Sarubbo
2021-01-24 0:34 Sam James
2021-01-24 0:34 Sam James
2021-01-22 23:01 Sam James
2020-12-17 14:12 Joonas Niilola
2020-11-08 12:02 Sam James
2020-11-05 12:32 Joonas Niilola
2020-10-09 7:25 Joonas Niilola
2020-10-09 7:25 Joonas Niilola
2020-10-09 7:25 Joonas Niilola
2020-09-02 22:43 Sam James
2020-09-02 22:43 Sam James
2020-08-02 4:08 Aaron Bauman
2020-06-20 17:42 Aaron Bauman
2020-06-20 17:42 Aaron Bauman
2020-06-04 7:56 Joonas Niilola
2019-11-17 22:32 Tim Harder
2019-11-17 22:32 Tim Harder
2019-01-31 9:17 Tim Harder
2019-01-19 3:22 Thomas Deutschmann
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=1701965769.c3d7778b6fdc3cb68163d8f65233b424f859b626.matthew@gentoo \
--to=matthew@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