From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Clightd: update to 5.8; Clight: update to 4.10.
Date: Fri, 23 Jun 2023 14:27:22 +0200 [thread overview]
Message-ID: <20230623122722.ZdbXnXelupSxAg3JF8DqKTW1WdI_Ti8X3-6DCzWkZAQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44572@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/44572#issuecomment-1604212242
Comment:
Could you change the maintainer to `Orphaned <orphan@voidlinux.org>` since they haven't contributed for some time now and only updated the first release?
next prev parent reply other threads:[~2023-06-23 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 19:05 [PR PATCH] " icp1994
2023-06-23 12:27 ` Duncaen [this message]
2023-06-23 19:13 ` [PR PATCH] [Updated] " icp1994
2023-06-23 19:13 ` icp1994
2023-06-23 19:19 ` [PR PATCH] [Merged]: " Duncaen
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=20230623122722.ZdbXnXelupSxAg3JF8DqKTW1WdI_Ti8X3-6DCzWkZAQ@z \
--to=duncaen@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).