From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: python3-pdm-2.18.2 and dependencies
Date: Wed, 25 Sep 2024 23:13:29 +0200 [thread overview]
Message-ID: <20240925211329.D6B6B22FDD@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52210@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/52210#issuecomment-2375266758
Comment:
There is no ETA for the merging of any PR, especially new packages.
I haven't looked at this at all. When I label PRs, it's usually from the list view. I don't have time to do a review of this PR now, so you'll have to wait for someone else to come along.
We also prefer that new packages be added by established contributors, so people don't add the package they want and disappear (leaving us to maintain it for you). I would suggest contributing changes to some existing packages first. A good way to do this is to look at the [list of available updates for unmaintained packages](https://repo-default.voidlinux.org/void-updates/void-updates/updates_orphan%40voidlinux.org.txt), the [list of open bug reports](https://github.com/void-linux/void-packages/issues?q=is%3Aopen+is%3Aissue+-label%3Arequest), or the [list of "good first issues"](https://github.com/void-linux/void-packages/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22).
next prev parent reply other threads:[~2024-09-25 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 18:36 [PR PATCH] " mmdbalkhi
2024-09-25 18:04 ` mmdbalkhi
2024-09-25 21:11 ` classabbyamp
2024-09-25 21:13 ` classabbyamp [this message]
2024-12-25 1:58 ` github-actions
2025-01-08 1:59 ` [PR PATCH] [Closed]: " github-actions
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=20240925211329.D6B6B22FDD@inbox.vuxu.org \
--to=classabbyamp@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).