From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gegl: enable vapigen
Date: Fri, 23 Sep 2022 09:42:54 +0200 [thread overview]
Message-ID: <20220923074254.Go1FtWh_0VMOGLGsS_9X0jsNrTUJZv1goWzKfm6GogE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39430@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/39430#issuecomment-1255892417
Comment:
Tests are failing because of the pango issue that would be resolved here: https://github.com/void-linux/void-packages/pull/39428
next prev parent reply other threads:[~2022-09-23 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 6:33 [PR PATCH] " oreo639
2022-09-23 7:30 ` [PR PATCH] [Updated] " oreo639
2022-09-23 7:42 ` oreo639
2022-09-23 7:42 ` oreo639 [this message]
2022-09-23 7:43 ` oreo639
2022-09-23 7:48 ` [PR PATCH] [Updated] " oreo639
2022-09-23 8:10 ` [PR PATCH] [Merged]: " paper42
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=20220923074254.Go1FtWh_0VMOGLGsS_9X0jsNrTUJZv1goWzKfm6GogE@z \
--to=oreo639@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).