From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: ibus-chewing
Date: Sun, 27 Nov 2022 17:40:48 +0100 [thread overview]
Message-ID: <20221127164048.0imhxtziE9x04crlCQOrOdvnnDQ6ocRiTOBsPZiElsQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40710@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
New review comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/40710#discussion_r1032966211
Comment:
No, that's equivalent to just not using a release. A release is required because the developers know the best when the code is stable and usable. If we packaged the latest commit, we would have to figure out issues on our own and the maintenance burden would be much higher.
next prev parent reply other threads:[~2022-11-27 16:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 15:31 [PR PATCH] New package: ibus-chewing, ibus-array: add runtime dep funk443
2022-11-23 17:26 ` [PR REVIEW] " oreo639
2022-11-23 17:26 ` oreo639
2022-11-23 17:26 ` oreo639
2022-11-23 17:26 ` oreo639
2022-11-23 17:26 ` oreo639
2022-11-23 17:27 ` oreo639
2022-11-23 17:28 ` oreo639
2022-11-23 17:32 ` oreo639
2022-11-23 17:33 ` oreo639
2022-11-23 17:34 ` oreo639
2022-11-24 0:10 ` classabbyamp
2022-11-24 3:24 ` sgn
2022-11-24 4:08 ` [PR PATCH] [Updated] " funk443
2022-11-24 4:14 ` funk443
2022-11-24 11:12 ` funk443
2022-11-24 11:13 ` [PR REVIEW] " classabbyamp
2022-11-24 11:18 ` [PR PATCH] [Updated] " funk443
2022-11-24 11:18 ` funk443
2022-11-24 11:20 ` [PR PATCH] [Updated] New package: ibus-chewing funk443
2022-11-24 11:21 ` [PR REVIEW] " funk443
2022-11-24 12:00 ` [PR PATCH] [Updated] " funk443
2022-11-24 12:10 ` [PR REVIEW] " Duncaen
2022-11-24 12:34 ` funk443
2022-11-24 12:42 ` [PR PATCH] [Updated] " funk443
2022-11-24 20:02 ` [PR REVIEW] " oreo639
2022-11-24 20:09 ` oreo639
2022-11-25 5:08 ` funk443
2022-11-25 5:11 ` funk443
2022-11-25 5:12 ` funk443
2022-11-27 15:33 ` [PR PATCH] [Updated] " funk443
2022-11-27 16:02 ` [PR REVIEW] " paper42
2022-11-27 16:04 ` paper42
2022-11-27 16:30 ` funk443
2022-11-27 16:40 ` paper42 [this message]
2022-11-27 16:51 ` funk443
2022-11-27 16:55 ` paper42
2022-11-27 16:56 ` classabbyamp
2022-11-27 16:57 ` funk443
2022-11-27 16:57 ` [PR PATCH] [Closed]: " funk443
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=20221127164048.0imhxtziE9x04crlCQOrOdvnnDQ6ocRiTOBsPZiElsQ@z \
--to=paper42@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).