Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: rockpass-0.10.0
Date: Sat, 01 Feb 2025 17:09:00 +0100	[thread overview]
Message-ID: <20250201160900.60FAB23D6C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54167@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/54167#issuecomment-2629009806

Comment:
@elbachir-one, I've warned you before against firing off new-package PRs in response to recently opened package requests. We are not interested in "throw it over the wall" submissions and your history of contributions makes it har dot believe submissions of this nature are anything else.

@Eloitor, you maintain several packages and have made numerous contributions to the Void repository. At the same time, you dominate our issue page with something like 90 new-package requests. In general, requests ought to be reserved for those who lack experience and knowledge to do the work themselves, or for *occasional* calls for assistance when complexity or time constraints prevent the requester from doing the work. Please, from now on, give more thought to whether you are willing to undertake the work you're asking to be done. If so, submit pull requests, not issues; if not, the package probably isn't important enough to be asking others for it.

  

      parent reply	other threads:[~2025-02-01 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 23:04 [PR PATCH] " elbachir-one
2025-02-01  8:14 ` Eloitor
2025-02-01 16:09 ` [PR PATCH] [Closed]: " ahesford
2025-02-01 16:09 ` ahesford [this message]

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=20250201160900.60FAB23D6C@inbox.vuxu.org \
    --to=ahesford@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).