From: DragonGhost7 <DragonGhost7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: notmuch: update to 0.38.1, adopt.
Date: Mon, 30 Oct 2023 00:59:32 +0100 [thread overview]
Message-ID: <20231029235932.0Nj5dN8mftfRjeNHaMYuoaN2sZ0RPZDJcRWkT_2Hs20@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46963@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
New comment by DragonGhost7 on void-packages repository
https://github.com/void-linux/void-packages/pull/46963#issuecomment-1784280908
Comment:
Huh.
T050-new.19 test fails because the error message has a lines displayed in the wrong line?
Not sure how this happens.
T760-as-text.10 test
fails because of an incorrect regex interpretation of the message? also very fully not sure why.
Do not know how other *-musl build check phase went since they were skipped because of cross-builds.
next prev parent reply other threads:[~2023-10-29 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 20:35 [PR PATCH] " DragonGhost7
2023-10-29 23:59 ` DragonGhost7 [this message]
2023-10-30 2:35 ` [PR PATCH] [Updated] " DragonGhost7
2023-10-30 2:42 ` DragonGhost7
2024-01-29 1:45 ` github-actions
2024-02-13 1:45 ` [PR PATCH] [Closed]: " github-actions
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=20231029235932.0Nj5dN8mftfRjeNHaMYuoaN2sZ0RPZDJcRWkT_2Hs20@z \
--to=dragonghost7@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).