From: CameronNemo <CameronNemo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] gcc: disable libssp
Date: Tue, 17 Jan 2023 03:37:40 +0100 [thread overview]
Message-ID: <20230117023740.HbPLyJFSSnZM60-boV00UceIou6J0FBAQe4hb50OAQw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41294@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
New review comment by CameronNemo on void-packages repository
https://github.com/void-linux/void-packages/pull/41294#discussion_r1071687149
Comment:
>I will cease maintenance of the project as a whole beginning January 2023.
>
>That means if the project is to continue, somebody else will have to take over. They will need to provide their own build infrastructure as well as everything else, as the public repository hosting will be shutting down as well.
https://voidlinux-ppc.org/news/2022/09/repo-update.html
next prev parent reply other threads:[~2023-01-17 2:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 2:16 [PR PATCH] " oreo639
2022-12-26 2:34 ` [PR PATCH] [Updated] " oreo639
2022-12-26 7:26 ` oreo639
2022-12-26 7:57 ` oreo639
2022-12-26 8:07 ` oreo639
2022-12-26 8:22 ` oreo639
2022-12-26 8:29 ` oreo639
2022-12-26 8:43 ` oreo639
2022-12-26 8:54 ` oreo639
2022-12-26 9:04 ` oreo639
2022-12-26 9:19 ` oreo639
2022-12-26 11:47 ` oreo639
2022-12-26 21:42 ` oreo639
2022-12-26 23:30 ` oreo639
2022-12-27 1:53 ` oreo639
2022-12-27 5:18 ` oreo639
2022-12-27 7:10 ` oreo639
2022-12-27 8:40 ` oreo639
2022-12-27 17:17 ` [PR REVIEW] " paper42
2022-12-27 22:29 ` oreo639
2022-12-27 22:30 ` oreo639
2022-12-27 22:32 ` [PR PATCH] [Updated] " oreo639
2023-01-09 16:24 ` oreo639
2023-01-09 16:28 ` oreo639
2023-01-09 17:47 ` oreo639
2023-01-09 18:19 ` oreo639
2023-01-17 2:37 ` CameronNemo [this message]
2023-01-17 2:40 ` [PR REVIEW] " CameronNemo
2023-01-17 2:42 ` oreo639
2023-01-17 2:43 ` oreo639
2023-01-17 2:44 ` oreo639
2023-01-17 2:45 ` oreo639
2023-01-17 2:45 ` oreo639
2023-01-17 2:46 ` oreo639
2023-01-17 2:53 ` oreo639
2023-01-17 2:53 ` oreo639
2023-01-17 2:56 ` CameronNemo
2023-01-21 2:03 ` [PR PATCH] [Updated] " oreo639
2023-01-21 2:04 ` [PR REVIEW] " oreo639
2023-01-21 17:37 ` [PR PATCH] [Updated] " oreo639
2023-01-22 5:59 ` [PR REVIEW] " sgn
2023-01-22 7:27 ` [PR PATCH] [Updated] " oreo639
2023-02-05 23:34 ` oreo639
2023-02-12 3:36 ` oreo639
2023-02-12 5:35 ` sgn
2023-02-12 6:04 ` sgn
2023-02-12 6:05 ` sgn
2023-02-12 6:05 ` [PR PATCH] [Merged]: " sgn
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=20230117023740.HbPLyJFSSnZM60-boV00UceIou6J0FBAQe4hb50OAQw@z \
--to=cameronnemo@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).