From: AnInternetTroll <AnInternetTroll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: neomutt: update to 20231103
Date: Sun, 19 Nov 2023 10:46:30 +0100 [thread overview]
Message-ID: <20231119094630.Vq3AcauJ_AXMK12kemNeo0UcOgU52cf8pozk4akSvFc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46668@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
New comment by AnInternetTroll on void-packages repository
https://github.com/void-linux/void-packages/pull/46668#issuecomment-1817803311
Comment:
On Sat, Nov 18, 2023 at 10:48:55PM -0800, Toyam Cox wrote:
>Can you please give clarity on that patch, which seems to fix a bug in 1103 that we could avoid by being on 1023 without a real loss of functionality, yes?
Well 1103 does introduce like 4 new features. But it might be safer to
stay on 1023 until that patch comes in a full release.
Just tested 1023 and it doesn't require any patches to build and test
locally, so that seems like the best option.
next prev parent reply other threads:[~2023-11-19 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 21:34 [PR PATCH] WIP neomutt: update to 202310065 AnInternetTroll
2023-10-13 21:52 ` [PR PATCH] [Updated] " AnInternetTroll
2023-10-13 22:06 ` AnInternetTroll
2023-10-14 7:24 ` AnInternetTroll
2023-11-15 21:06 ` [PR PATCH] [Updated] " AnInternetTroll
2023-11-15 21:11 ` [PR PATCH] [Updated] neomutt: update to 20231103 AnInternetTroll
2023-11-15 21:16 ` AnInternetTroll
2023-11-16 14:33 ` Vaelatern
2023-11-16 14:34 ` [PR REVIEW] " Vaelatern
2023-11-19 6:48 ` Vaelatern
2023-11-19 6:48 ` Vaelatern
2023-11-19 9:44 ` AnInternetTroll
2023-11-19 9:46 ` AnInternetTroll [this message]
2023-11-19 9:46 ` [PR PATCH] [Updated] " AnInternetTroll
2023-11-19 20:59 ` [PR PATCH] [Merged]: neomutt: update to 20231023 Vaelatern
2023-11-19 20:59 ` Vaelatern
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=20231119094630.Vq3AcauJ_AXMK12kemNeo0UcOgU52cf8pozk4akSvFc@z \
--to=aninternettroll@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).