Github messages for voidlinux
 help / color / mirror / Atom feed
From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hexchat: update to 2.16.2.
Date: Wed, 14 Feb 2024 08:22:35 +0100	[thread overview]
Message-ID: <20240214072235.4786E274B1@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48709@inbox.vuxu.org>

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

New comment by 0x5c on void-packages repository

https://github.com/void-linux/void-packages/pull/48709#issuecomment-1943208340

Comment:
While package update PRs from new contributors are generally appreciated, please don't do that for recently released versions of packages with active maintainers. Especially if the update is less than ~1month and you answer "briefly" to the question about testing.

Instead, target packages that are orphaned, and/or have had an update available for months; other than core packages like glibc/musl/gcc/llvm/rust/etc, those updates tend to be easy and very appreciated. Sometimes those packages don't get the attention they should have.
If you build a history of contribution to void, you could even [adopt](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#adopting-a-template) one of them and [submit new packages](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#creating-a-new-template).

As for this update specifically, there's no rush; it's not like there'd be a new update two days after merging this one. I can take the time to properly test the update and gather patches to fix bugs that we normally would rely on being fixed upstream.

  parent reply	other threads:[~2024-02-14  7:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 22:14 [PR PATCH] " caughtquick
2024-02-13 22:18 ` classabbyamp
2024-02-13 23:11 ` caughtquick
2024-02-13 23:15 ` [PR PATCH] [Updated] " caughtquick
2024-02-14  7:22 ` 0x5c [this message]
2024-02-14  7:24 ` caughtquick
2024-02-14  7:24 ` caughtquick
2024-02-14  7:25 ` 0x5c
2024-02-14  7:27 ` [PR PATCH] [Closed]: " caughtquick
2024-02-18 12:19 [PR PATCH] " zlice
2024-02-18 12:21 ` 0x5c

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=20240214072235.4786E274B1@inbox.vuxu.org \
    --to=0x5c@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).