From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: portage: update to 3.0.39.
Date: Mon, 28 Nov 2022 10:55:35 +0100 [thread overview]
Message-ID: <20221128095535.9QeeFcXuLcKGW_dhMclEACepLwDCUWKHieT_sb8Unew@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38353@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
New comment by teldra on void-packages repository
https://github.com/void-linux/void-packages/pull/38353#issuecomment-1328807008
Comment:
https://github.com/void-linux/void-packages/actions/runs/3563522088/jobs/5986400166
fails on multiple tests
next prev parent reply other threads:[~2022-11-28 9:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 16:49 [PR PATCH] portage: update to 3.0.34 teldra
2022-07-29 18:20 ` [PR PATCH] [Updated] " teldra
2022-07-29 18:40 ` teldra
2022-07-29 18:43 ` teldra
2022-07-30 6:02 ` teldra
2022-07-30 7:35 ` teldra
2022-07-30 7:52 ` teldra
2022-07-30 18:22 ` teldra
2022-10-04 6:26 ` teldra
2022-10-04 6:27 ` teldra
2022-10-04 6:29 ` teldra
2022-10-04 6:40 ` teldra
2022-10-04 6:52 ` teldra
2022-10-04 9:04 ` teldra
2022-10-04 9:05 ` teldra
2022-10-04 9:28 ` teldra
2022-10-04 9:28 ` teldra
2022-10-09 6:21 ` teldra
2022-10-09 6:22 ` teldra
2022-10-09 6:57 ` teldra
2022-10-09 7:09 ` teldra
2022-10-09 7:25 ` teldra
2022-10-09 7:40 ` teldra
2022-10-09 7:54 ` teldra
2022-10-09 7:55 ` teldra
2022-11-26 1:20 ` [PR PATCH] [Updated] portage: update to 3.0.38.1 teldra
2022-11-28 9:40 ` [PR PATCH] [Updated] portage: update to 3.0.39 teldra
2022-11-28 9:55 ` teldra [this message]
2022-11-28 9:55 ` teldra
2023-01-25 16:43 ` liarimu
2023-01-26 20:43 ` liarimu
2023-01-27 9:34 ` liarimu
2023-02-10 12:36 ` [PR PATCH] [Updated] " teldra
2023-02-10 12:38 ` teldra
2023-02-10 18:09 ` [PR PATCH] [Merged]: portage: update to 3.0.44 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=20221128095535.9QeeFcXuLcKGW_dhMclEACepLwDCUWKHieT_sb8Unew@z \
--to=teldra@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).