From: wael444 <wael444@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Llvm13
Date: Sun, 27 Mar 2022 11:19:55 +0200 [thread overview]
Message-ID: <20220327091955.7m4fBUAtjB-k5NpaEsbUGf9jC33AgefhdU_yJqMGopM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36229@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
New comment by wael444 on void-packages repository
https://github.com/void-linux/void-packages/pull/36229#issuecomment-1079889653
Comment:
How come LLVM13 for Void Linux is taking this long to get added? is it not receiving the attention it needs from the primary maintainers?
next prev parent reply other threads:[~2022-03-27 9:19 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 20:12 [PR PATCH] Llvm13 motorto
2022-03-20 7:58 ` Llvm13 dkwo
2022-03-20 14:03 ` Llvm13 motorto
2022-03-20 16:23 ` Llvm13 motorto
2022-03-20 17:59 ` Llvm13 dkwo
2022-03-21 7:20 ` Llvm13 dkwo
2022-03-21 7:28 ` Llvm13 dkwo
2022-03-21 8:35 ` Llvm13 dkwo
2022-03-21 8:48 ` Llvm13 motorto
2022-03-21 8:56 ` Llvm13 dkwo
2022-03-21 9:44 ` Llvm13 dkwo
2022-03-21 9:50 ` Llvm13 dkwo
2022-03-21 9:57 ` Llvm13 dkwo
2022-03-21 10:53 ` Llvm13 sgn
2022-03-21 12:27 ` Llvm13 dkwo
2022-03-23 14:38 ` Llvm13 dkwo
2022-03-23 16:08 ` Llvm13 dkwo
2022-03-24 14:56 ` Llvm13 motorto
2022-03-27 9:19 ` wael444 [this message]
2022-03-27 9:23 ` Llvm13 wael444
2022-03-27 9:41 ` Llvm13 Anachron
2022-03-27 10:47 ` Llvm13 wael444
2022-03-27 11:06 ` Llvm13 wael444
2022-03-27 11:29 ` Llvm13 q66
2022-03-27 11:56 ` Llvm13 dkwo
2022-03-27 14:20 ` Llvm13 ifreund
2022-03-27 14:41 ` Llvm13 motorto
2022-03-27 15:05 ` Llvm13 motorto
2022-03-27 16:02 ` Llvm13 wael444
2022-03-27 18:52 ` Llvm13 dkwo
2022-03-27 19:12 ` Llvm13 wael444
2022-03-28 7:17 ` Llvm13 dkwo
2022-03-28 14:16 ` Llvm13 motorto
2022-03-28 18:45 ` Llvm13 wael444
2022-03-28 18:52 ` Llvm13 wael444
2022-03-28 18:58 ` Llvm13 wael444
2022-03-28 19:19 ` Llvm13 wael444
2022-03-29 8:28 ` [PR PATCH] [Updated] Llvm13 motorto
2022-03-29 8:29 ` Llvm13 motorto
2022-03-29 8:52 ` Llvm13 dkwo
2022-03-29 10:19 ` Llvm13 wael444
2022-03-29 14:04 ` Llvm13 subnut
2022-03-29 14:51 ` Llvm13 motorto
2022-03-30 14:20 ` Llvm13 motorto
2022-03-30 14:36 ` Llvm13 motorto
2022-03-30 14:47 ` Llvm13 dkwo
2022-03-30 14:48 ` Llvm13 motorto
2022-03-30 14:48 ` Llvm13 motorto
2022-03-30 14:51 ` Llvm13 motorto
2022-03-30 14:53 ` Llvm13 dkwo
2022-03-30 15:11 ` Llvm13 motorto
2022-03-30 16:57 ` Llvm13 motorto
2022-03-30 20:48 ` [PR PATCH] [Updated] Llvm13 motorto
2022-03-30 20:49 ` Llvm13 motorto
2022-03-30 20:50 ` [PR PATCH] [Updated] Llvm13 motorto
2022-03-30 20:51 ` motorto
2022-03-30 20:52 ` Llvm13 motorto
2022-03-31 6:20 ` [PR PATCH] [Updated] Llvm13 motorto
2022-03-31 6:20 ` Llvm13 motorto
2022-03-31 8:02 ` Llvm13 motorto
2022-03-31 16:03 ` [PR PATCH] [Updated] Llvm13 motorto
2022-03-31 18:55 ` motorto
2022-03-31 18:56 ` Llvm13 motorto
2022-03-31 18:57 ` Llvm13 motorto
2022-03-31 21:16 ` [PR PATCH] [Updated] Llvm13 motorto
2022-04-01 7:37 ` Llvm13 dkwo
2022-04-01 7:43 ` Llvm13 motorto
2022-04-01 7:58 ` Llvm13 dkwo
2022-04-01 8:36 ` [PR PATCH] [Updated] Llvm13 motorto
2022-04-01 8:36 ` Llvm13 motorto
2022-04-01 10:13 ` Llvm13 wael444
2022-04-01 10:59 ` Llvm13 motorto
2022-04-01 11:30 ` Llvm13 wael444
2022-04-09 21:40 ` Llvm13 JavaLich
2022-04-29 4:39 ` Llvm13 corbmr
2022-04-29 6:10 ` Llvm13 motorto
2022-05-12 20:14 ` Llvm13 motorto
2022-05-18 18:39 ` Llvm13 Nairou
2022-05-19 14:56 ` Llvm13 motorto
2022-05-19 15:10 ` Llvm13 dkwo
2022-05-19 15:42 ` Llvm13 motorto
2022-05-21 16:11 ` Llvm13 ericonr
2022-05-21 16:11 ` Llvm13 ericonr
2022-05-22 8:58 ` [PR PATCH] [Updated] Llvm13 motorto
2022-05-22 9:02 ` Llvm13 motorto
2022-05-22 9:07 ` Llvm13 q66
2022-05-22 16:52 ` Llvm13 motorto
2022-05-22 16:52 ` [PR PATCH] [Closed]: Llvm13 motorto
2022-05-23 0:18 ` Llvm13 Nairou
2022-05-23 8:14 ` Llvm13 motorto
2022-05-23 8:50 ` Llvm13 q66
2022-05-23 8:51 ` Llvm13 q66
2022-05-23 10:02 ` Llvm13 motorto
2022-05-23 10:02 ` Llvm13 motorto
2022-05-23 10:06 ` Llvm13 q66
2022-05-23 10:11 ` Llvm13 ifreund
2022-05-23 10:20 ` Llvm13 q66
2022-06-13 10:07 ` Llvm13 dkwo
2022-06-23 21:50 ` Llvm13 gbrlsnchs
2022-06-24 14:14 ` Llvm13 dkwo
2022-10-11 7:20 ` Llvm13 motorto
-- strict thread matches above, loose matches on Subject: below --
2022-02-28 21:56 [PR PATCH] Llvm13 motorto
2022-03-02 11:57 ` Llvm13 ifreund
2022-03-02 20:22 ` Llvm13 ifreund
2022-03-02 20:24 ` Llvm13 ifreund
2022-03-02 20:25 ` Llvm13 ifreund
2022-03-03 18:27 ` Llvm13 Johnnynator
2022-03-04 12:06 ` Llvm13 motorto
2022-03-04 12:18 ` Llvm13 motorto
2022-03-17 15:00 ` Llvm13 dkwo
2022-03-19 20:13 ` Llvm13 motorto
2022-03-29 14:00 ` Llvm13 subnut
2022-03-29 14:01 ` Llvm13 subnut
2022-03-29 14:02 ` Llvm13 subnut
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=20220327091955.7m4fBUAtjB-k5NpaEsbUGf9jC33AgefhdU_yJqMGopM@z \
--to=wael444@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).