From: ii8 <ii8@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: mlton-20210117
Date: Tue, 07 Nov 2023 18:35:36 +0100 [thread overview]
Message-ID: <20231107173536.61VfLPipQ3sc7UpqA1bll4_O_OEvVmR1L19K6VWUgT8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46951@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
New comment by ii8 on void-packages repository
https://github.com/void-linux/void-packages/pull/46951#issuecomment-1799293094
Comment:
I don't mind either way, just mentioning the options. But I should mention that bootstrapping mlton with itself is recommended by the author and polyml fails for x86.
Where should it be hosted? Though it's several files of generated sml, just all in one patch.
The patch can be cherry picked from upstream, that's one option.
next prev parent reply other threads:[~2023-11-07 17:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 19:09 [PR PATCH] " ii8
2023-10-28 20:36 ` [PR PATCH] [Updated] " ii8
2023-10-29 8:04 ` Bnyro
2023-11-07 16:40 ` leahneukirchen
2023-11-07 17:14 ` ii8
2023-11-07 17:17 ` leahneukirchen
2023-11-07 17:17 ` leahneukirchen
2023-11-07 17:28 ` ii8
2023-11-07 17:35 ` ii8 [this message]
2023-11-07 17:40 ` leahneukirchen
2023-11-07 23:40 ` [PR PATCH] [Updated] " ii8
2023-11-08 0:33 ` ii8
2023-11-08 12:15 ` leahneukirchen
2023-11-08 12:16 ` leahneukirchen
2023-11-08 12:26 ` ii8
2023-11-08 12:30 ` leahneukirchen
2023-11-08 13:40 ` [PR PATCH] [Updated] " ii8
2023-12-01 13:10 ` [PR PATCH] [Merged]: " leahneukirchen
2023-12-01 14:54 ` leahneukirchen
2023-12-01 21:26 ` ii8
2023-12-02 17:58 ` leahneukirchen
-- strict thread matches above, loose matches on Subject: below --
2023-06-24 22:59 [PR PATCH] New Package: mlton-20210117 CabrioletDiskette
2023-09-27 1:45 ` github-actions
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=20231107173536.61VfLPipQ3sc7UpqA1bll4_O_OEvVmR1L19K6VWUgT8@z \
--to=ii8@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).