From: "Tim Harder" <radhermit@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-proxy/sshuttle/
Date: Mon, 18 Nov 2019 06:29:03 +0000 (UTC) [thread overview]
Message-ID: <1574058535.8f2addacc3038dbfc5b180493bbc09f3032b22a4.radhermit@gentoo> (raw)
commit: 8f2addacc3038dbfc5b180493bbc09f3032b22a4
Author: Tim Harder <radhermit <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 18 06:27:38 2019 +0000
Commit: Tim Harder <radhermit <AT> gentoo <DOT> org>
CommitDate: Mon Nov 18 06:28:55 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8f2addac
net-proxy/sshuttle: drop myself as a maintainer
Signed-off-by: Tim Harder <radhermit <AT> gentoo.org>
net-proxy/sshuttle/metadata.xml | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/net-proxy/sshuttle/metadata.xml b/net-proxy/sshuttle/metadata.xml
index 6956e63728a..7597a9dccda 100644
--- a/net-proxy/sshuttle/metadata.xml
+++ b/net-proxy/sshuttle/metadata.xml
@@ -1,10 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>radhermit@gentoo.org</email>
- <name>Tim Harder</name>
- </maintainer>
+ <!-- maintainer-needed -->
<upstream>
<remote-id type="pypi">sshuttle</remote-id>
<remote-id type="github">sshuttle/sshuttle</remote-id>
next reply other threads:[~2019-11-18 6:29 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 6:29 Tim Harder [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-25 6:01 [gentoo-commits] repo/gentoo:master commit in: net-proxy/sshuttle/ Sam James
2025-05-25 6:01 Sam James
2025-04-22 5:56 Sam James
2025-04-22 4:42 Sam James
2025-03-20 3:51 Sam James
2024-07-17 5:54 Sam James
2024-07-17 5:54 Sam James
2024-04-29 13:42 Sam James
2024-04-29 5:48 Sam James
2024-02-21 10:17 Sam James
2023-03-17 5:32 Michał Górny
2022-10-28 19:53 Sam James
2022-10-08 23:10 Sam James
2022-10-08 23:10 Sam James
2022-09-06 2:16 Sam James
2022-04-29 10:21 Sam James
2022-03-02 3:42 Sam James
2022-03-02 3:42 Sam James
2022-01-28 8:17 Sam James
2021-08-21 13:29 Arthur Zamarin
2021-05-28 3:21 Sam James
2021-05-17 1:09 Sam James
2021-03-16 21:28 Sam James
2021-03-16 21:28 Sam James
2021-02-02 23:51 Sam James
2021-02-02 23:46 Sam James
2021-01-31 21:51 Sam James
2020-12-29 20:15 Sam James
2020-12-27 4:47 Sam James
2020-12-27 4:31 Sam James
2020-09-20 20:21 Agostino Sarubbo
2020-08-30 1:32 Thomas Deutschmann
2020-08-02 23:08 Sam James
2020-08-02 22:49 Sam James
2020-02-11 12:16 Michał Górny
2019-08-14 23:17 Tim Harder
2019-06-09 22:13 Tim Harder
2019-04-03 4:46 Tim Harder
2019-04-03 4:46 Tim Harder
2019-03-04 8:34 Tim Harder
2018-12-28 10:13 Tim Harder
2018-12-28 10:13 Tim Harder
2018-06-30 17:34 Tim Harder
2018-03-23 6:39 Tim Harder
2018-03-23 6:39 Tim Harder
2018-02-06 3:18 Tim Harder
2017-08-31 14:30 Tim Harder
2017-08-31 14:30 Tim Harder
2017-07-29 4:51 Tim Harder
2016-11-23 5:15 Tim Harder
2016-11-23 5:15 Tim Harder
2016-08-10 3:06 Tim Harder
2016-08-06 7:37 Tim Harder
2016-08-06 7:37 Tim Harder
2016-04-08 5:14 Tim Harder
2016-03-12 7:03 Tim Harder
2016-03-12 7:00 Tim Harder
2016-01-19 4:44 Tim Harder
2016-01-19 4:28 Tim Harder
2016-01-13 21:58 Tim Harder
2016-01-10 2:52 Tim Harder
2015-11-28 0:56 Tim Harder
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=1574058535.8f2addacc3038dbfc5b180493bbc09f3032b22a4.radhermit@gentoo \
--to=radhermit@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