From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: .NET Core
Date: Thu, 07 Oct 2021 16:13:47 +0200 [thread overview]
Message-ID: <20211007141347.8_V4e8qYe9Cc2mdZHXtZ8w8vjG40S2vtBbX5b0wsDQU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-10773@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 382 bytes --]
New comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/issues/10773#issuecomment-937834567
Comment:
> Can we reopen this? the merge was reverted because of a whole host of issues. The major one being that it didn't seem to support libressl.
So, now that Void has migrated back to OpenSSL, is it worth it taking another shot at this?
next prev parent reply other threads:[~2021-10-07 14:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-10773@inbox.vuxu.org>
2019-06-23 3:26 ` voidlinux-github
2019-06-24 5:40 ` voidlinux-github
2020-02-28 15:51 ` Sarkasper
2020-03-11 18:11 ` toluschr
2020-05-08 3:53 ` Luxed
2020-05-08 5:44 ` Cogitri
2020-05-09 3:35 ` Luxed
2020-05-18 14:55 ` hatf0
2020-05-19 18:59 ` agausmann
2020-05-19 19:00 ` agausmann
2020-05-23 7:50 ` Johnnynator
2020-05-23 7:56 ` agausmann
2020-07-03 12:23 ` aquaspy
2020-07-04 11:02 ` toluschr
2020-08-08 11:21 ` toluschr
2021-10-07 14:13 ` jcgruenhage [this message]
2022-04-15 0:51 ` github-actions
2022-04-15 2:21 ` ThePademelon
2022-07-31 14:41 ` Nathan-MV
2023-09-18 18:36 ` lissine0
2023-09-18 20:02 ` Anachron
2023-10-26 19:12 ` IcedQuinn
2023-10-26 20:13 ` lissine0
2023-10-26 23:03 ` IcedQuinn
2023-10-27 11:02 ` lissine0
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=20211007141347.8_V4e8qYe9Cc2mdZHXtZ8w8vjG40S2vtBbX5b0wsDQU@z \
--to=jcgruenhage@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).