From: necrophcodr <necrophcodr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fail2ban: change maintainer
Date: Fri, 07 Jul 2023 18:14:53 +0200 [thread overview]
Message-ID: <20230707161453.W8WQc-69pg7OgnLXSz3GpM-Yb7l7P3R_NDzoyD6sgUM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44894@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
New comment by necrophcodr on void-packages repository
https://github.com/void-linux/void-packages/pull/44894#issuecomment-1625643738
Comment:
> We generally don't want to change maintainer ship for packages to people who are really new, there has a been a history of one-of maintainers adopting packages and then not contributing anymore.
On the other hand, I haven't been maintaining that package. Is it better to keep a maintainer that, for years, hasn't actively contributed?
next prev parent reply other threads:[~2023-07-07 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 6:26 [PR PATCH] " MeganerdNL
2023-07-07 6:49 ` necrophcodr
2023-07-07 13:00 ` Duncaen
2023-07-07 13:38 ` MeganerdNL
2023-07-07 16:14 ` necrophcodr [this message]
2023-07-07 16:32 ` Duncaen
2023-07-07 19:44 ` necrophcodr
2023-07-07 19:45 ` necrophcodr
2023-07-09 7:48 ` classabbyamp
2023-07-09 8:06 ` [PR PATCH] [Closed]: " MeganerdNL
2023-07-09 8:06 ` [PR PATCH] [Updated] " MeganerdNL
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=20230707161453.W8WQc-69pg7OgnLXSz3GpM-Yb7l7P3R_NDzoyD6sgUM@z \
--to=necrophcodr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).