From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dpkg: Add zstd compression
Date: Thu, 31 Dec 2020 23:09:17 +0100 [thread overview]
Message-ID: <20201231220917.sNkjvcSYL4nuGt_9iizECX0fFi5wgZZPEKJNTVprwyo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27584@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/27584#issuecomment-753216000
Comment:
You are free to run your own patched build, patching in features into random packages is not something that Void does.
If the patch is thoroughly tested and used a lot why is it not upstreamed? This would be a better approach than requesting random patches being added to random linux distributions.
prev parent reply other threads:[~2020-12-31 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 21:31 [PR PATCH] " CRKatri
2020-12-31 21:34 ` ericonr
2020-12-31 21:51 ` CRKatri
2020-12-31 21:59 ` Duncaen
2020-12-31 21:59 ` Duncaen
2020-12-31 22:06 ` Diatrus
2020-12-31 22:07 ` the-maldridge
2020-12-31 22:07 ` [PR PATCH] [Closed]: " the-maldridge
2020-12-31 22:09 ` Duncaen [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=20201231220917.sNkjvcSYL4nuGt_9iizECX0fFi5wgZZPEKJNTVprwyo@z \
--to=duncaen@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).