From: enguerrand <enguerrand@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Orphan enguerrand's packages
Date: Tue, 10 Jan 2023 15:34:09 +0100 [thread overview]
Message-ID: <20230110143409.2Q-7odT5DyhirlxzbYrsImiEgiIo4v8UJDbn6st7r8o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41539@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
New comment by enguerrand on void-packages repository
https://github.com/void-linux/void-packages/pull/41539#issuecomment-1377371709
Comment:
I am fine with this.
I got frustrated after investing quite some time into a PR which did not get merged for ages and then someone else made the required changes to update the package. (I understand that these things happen in projects run by volunteers but it was frustrating / discouraging nonetheless)
That being said I wouldn't find the time to maintain packages these days anymore, so it makes sense to orphan my packages either way.
next prev parent reply other threads:[~2023-01-10 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 15:29 [PR PATCH] " paper42
2023-01-10 14:34 ` enguerrand [this message]
2023-01-12 5:08 ` [PR PATCH] [Closed]: " classabbyamp
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=20230110143409.2Q-7odT5DyhirlxzbYrsImiEgiIo4v8UJDbn6st7r8o@z \
--to=enguerrand@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).