From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cherrytree: update to 0.99.51
Date: Sat, 19 Nov 2022 04:37:36 +0100 [thread overview]
Message-ID: <20221119033736.xJkREcQOMUYrbJ16YLMfEZH9uJjkf2kN7lOMq1Okzy0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40444@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 322 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/40444#issuecomment-1320780376
Comment:
> Could you report that upstream, that sounds like a bug.
Actually that was me misreading `cmakelists.txt`. The part about tests running during the build process is still true.
next prev parent reply other threads:[~2022-11-19 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 16:35 [PR PATCH] " cinerea0
2022-11-17 13:13 ` paper42
2022-11-19 3:36 ` [PR PATCH] [Updated] " cinerea0
2022-11-19 3:37 ` cinerea0 [this message]
2022-11-24 7:52 ` [PR PATCH] [Merged]: " classabbyamp
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=20221119033736.xJkREcQOMUYrbJ16YLMfEZH9uJjkf2kN7lOMq1Okzy0@z \
--to=cinerea0@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).