From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lxd-to-incus fails on void linux
Date: Tue, 26 Mar 2024 03:32:56 +0100 [thread overview]
Message-ID: <20240326023256.D8254220DE@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49542@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/49542#issuecomment-2019275644
Comment:
The fact that the version packaged by Void lacks features found in later versions isn't a bug, and we have mechanisms to track outdated versions that don't require opening issues. In fact, filing issues to complain of outdated packages just distracts maintainers and buries real issues m, so please refrain from doing so in the future.
next prev parent reply other threads:[~2024-03-26 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 2:00 [ISSUE] " cmspam
2024-03-26 2:32 ` ahesford [this message]
2024-03-26 2:32 ` [ISSUE] [CLOSED] " ahesford
2024-03-26 10:42 ` ahesford
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=20240326023256.D8254220DE@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).