From: piekay <piekay@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] NetworkManager-openconnect: update to 1.2.10.
Date: Wed, 19 Jun 2024 14:57:39 +0200 [thread overview]
Message-ID: <20240619125739.D972F23C7D@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50876@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
New review comment by piekay on void-packages repository
https://github.com/void-linux/void-packages/pull/50876#discussion_r1646158364
Comment:
Broken blocks all installs independent of architecture, right?
I will set up a VM for testing in the next days. Since the old version is broken, does it make sense to release the working version only for these select architectures?
next prev parent reply other threads:[~2024-06-19 12:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 1:04 [PR PATCH] " piekay
2024-06-18 1:04 ` piekay
2024-06-18 2:30 ` [PR PATCH] [Updated] " piekay
2024-06-18 2:47 ` piekay
2024-06-18 3:04 ` piekay
2024-06-18 3:11 ` piekay
2024-06-18 3:23 ` piekay
2024-06-18 3:37 ` piekay
2024-06-18 3:39 ` [PR PATCH] [Updated] " piekay
2024-06-18 3:40 ` piekay
2024-06-18 3:46 ` piekay
2024-06-18 3:48 ` [PR REVIEW] " classabbyamp
2024-06-18 3:48 ` classabbyamp
2024-06-19 12:55 ` piekay
2024-06-19 12:56 ` piekay
2024-06-19 12:57 ` classabbyamp
2024-06-19 12:57 ` piekay [this message]
2024-06-19 12:58 ` piekay
2024-06-22 1:48 ` [PR PATCH] [Updated] " piekay
2024-06-22 1:51 ` piekay
2024-06-22 1:52 ` [PR PATCH] [Updated] " piekay
2024-06-22 1:54 ` piekay
2024-06-22 2:28 ` piekay
2024-06-22 5:34 ` classabbyamp
2024-06-22 5:35 ` classabbyamp
2024-06-22 5:36 ` classabbyamp
2024-06-22 5:48 ` [PR PATCH] [Updated] " classabbyamp
2024-06-22 6:14 ` classabbyamp
2024-06-22 6:14 ` [PR PATCH] [Updated] " classabbyamp
2024-06-22 7:02 ` classabbyamp
2024-06-24 22:59 ` piekay
2024-06-25 0:43 ` classabbyamp
2024-06-26 15:25 ` [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=20240619125739.D972F23C7D@inbox.vuxu.org \
--to=piekay@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).