From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] dmd: update to 2.094.1
Date: Mon, 26 Oct 2020 02:00:54 +0100 [thread overview]
Message-ID: <20201026010054.VreGM_VUQRDvZ-_13NE9KONVsufRvEtsxKOdKNiiESA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25878@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
New review comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/25878#discussion_r511675634
Comment:
Gah, that's terrible.
> (in the bootstrap compiler's druntime, of course)
Are you sure that's correct? The bootstrap compiler should be building the new compiler with its own library and headers, right? Could be interesting to see what happens if you patch it in `dmd`.
next prev parent reply other threads:[~2020-10-26 1:00 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 15:22 [PR PATCH] " aurieh
2020-10-25 16:45 ` aurieh
2020-10-25 18:40 ` aurieh
2020-10-25 19:36 ` [PR PATCH] [Updated] " aurieh
2020-10-26 0:41 ` [PR REVIEW] " sgn
2020-10-26 0:41 ` sgn
2020-10-26 0:41 ` sgn
2020-10-26 0:41 ` sgn
2020-10-26 0:42 ` ericonr
2020-10-26 0:42 ` ericonr
2020-10-26 0:42 ` ericonr
2020-10-26 0:47 ` aurieh
2020-10-26 0:48 ` aurieh
2020-10-26 0:51 ` aurieh
2020-10-26 0:52 ` aurieh
2020-10-26 0:56 ` aurieh
2020-10-26 1:00 ` ericonr [this message]
2020-10-26 1:01 ` ericonr
2020-10-26 1:06 ` aurieh
2020-10-26 1:38 ` ericonr
2020-10-26 10:30 ` aurieh
2020-10-26 10:50 ` aurieh
2020-10-26 12:32 ` ericonr
2020-10-26 14:59 ` aurieh
2020-10-27 12:49 ` [PR PATCH] [Updated] " aurieh
2020-10-27 14:26 ` [PR REVIEW] " ericonr
2020-10-27 14:26 ` ericonr
2020-10-27 14:26 ` ericonr
2020-10-27 14:44 ` sgn
2020-10-27 15:06 ` aurieh
2020-10-27 15:34 ` aurieh
2020-10-27 15:38 ` ericonr
2020-10-27 15:38 ` ericonr
2020-10-27 16:18 ` aurieh
2020-10-27 16:35 ` [PR PATCH] [Updated] " aurieh
2020-10-27 23:53 ` [PR REVIEW] " aurieh
2020-10-27 23:55 ` aurieh
2020-10-28 2:00 ` [PR REVIEW] " ericonr
2020-10-28 3:16 ` ericonr
2020-10-28 21:10 ` [PR PATCH] [Updated] " aurieh
2020-10-28 21:11 ` aurieh
2020-10-28 22:40 ` ericonr
2020-10-28 23:39 ` aurieh
2020-10-28 23:41 ` ericonr
2020-10-28 23:46 ` ericonr
2020-10-28 23:59 ` ericonr
2020-10-29 0:34 ` ericonr
2020-10-29 8:13 ` aurieh
2020-10-29 8:53 ` aurieh
2020-10-29 9:49 ` [PR PATCH] [Updated] " aurieh
2020-10-29 9:51 ` aurieh
2020-10-30 1:08 ` ericonr
2020-11-12 4:00 ` ericonr
2020-11-14 17:58 ` aurieh
2020-11-14 23:08 ` ericonr
2020-11-22 4:39 ` ericonr
2020-11-22 19:46 ` ericonr
2020-11-23 11:23 ` [PR PATCH] [Updated] " aurieh
2020-11-23 11:39 ` aurieh
2021-02-01 21:30 ` ericonr
2021-02-10 2:18 ` [PR PATCH] [Updated] " aurieh
2021-02-10 2:18 ` aurieh
2021-02-12 3:51 ` [PR PATCH] [Closed]: " ericonr
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=20201026010054.VreGM_VUQRDvZ-_13NE9KONVsufRvEtsxKOdKNiiESA@z \
--to=ericonr@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).