From: "Ludovic Courtès" <ludo@gnu.org>
To: "Orians, Jeremiah (DTMB)" <OriansJ@michigan.gov>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"andrius@stikonas.eu" <andrius@stikonas.eu>,
"jeremiah@pdp10.guru" <jeremiah@pdp10.guru>,
"bootstrappable@freelists.org" <bootstrappable@freelists.org>
Subject: Re: [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'
Date: Thu, 28 Jan 2021 14:40:44 +0100 [thread overview]
Message-ID: <87h7n1npr7.fsf@gnu.org> (raw)
In-Reply-To: <DM8PR09MB6840259B959882B3352A72A6C6A19@DM8PR09MB6840.namprd09.prod.outlook.com> (Jeremiah Orians's message of "Thu, 21 Jan 2021 17:52:18 +0000")
Hi,
"Orians, Jeremiah (DTMB)" <OriansJ@michigan.gov> skribis:
>> I see a fourth option, which is to keep both. :-)
> Might want to fix up the confusing naming in that case
Yes, that’s probably a good idea.
>> In effect, it seems there are now two diverging projects. I think that’s fine: more bootstrapping work and more diversity is better!
> Converging actually as they share the exact same goal of bootstrap from nothing and run MesCC
My understanding is that they are nevertheless two different development
branches; is that right?
>> For Guix, the Scheme-based approach Janneke et al. have been pursing remains the most attractive.
> And would be faster if MesCC running on guile was used as the lone bootstrap seed.
What do you mean? Faster in what sense?
Again I’m commenting as an enthusiastic outsider, so I may miss pieces
of the puzzle. My impression is that we have now two different things
called “Mes” and two different approaches to the whole issue, so it
might make sense to label them differently.
At any rate, thanks to all the bootstrappers for the amazing work!
Ludo’.
next prev parent reply other threads:[~2021-01-28 13:41 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 17:01 wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello' Jan Nieuwenhuizen
2021-01-05 0:49 ` [bootstrappable] " jeremiah
2021-01-05 16:58 ` Pierre Neidhardt
2021-01-06 11:32 ` [bootstrappable] " Ludovic Courtès
2021-01-06 11:46 ` [bootstrappable] " Andrius Štikonas via Development of GNU Guix and the GNU System distribution.
2021-01-06 14:03 ` Orians, Jeremiah (DTMB)
2021-01-14 21:37 ` Ludovic Courtès
2021-01-15 1:27 ` jeremiah
2021-01-21 11:09 ` Ludovic Courtès
2021-01-21 17:52 ` Orians, Jeremiah (DTMB)
2021-01-28 13:40 ` Ludovic Courtès [this message]
2021-01-28 13:44 ` Orians, Jeremiah (DTMB)
2021-01-06 14:38 ` [bootstrappable] " Paul Sherwood
2021-01-07 10:43 ` Jan Nieuwenhuizen
2021-01-07 20:10 ` [bootstrappable] " Danny Milosavljevic
2021-01-07 20:23 ` Danny Milosavljevic
2021-01-07 22:52 ` Danny Milosavljevic
2021-01-08 6:25 ` Jan Nieuwenhuizen
2021-01-08 8:05 ` [Tinycc-devel] " arnold
2021-01-08 13:02 ` Jan Nieuwenhuizen
2021-01-08 13:43 ` Danny Milosavljevic
2021-01-08 14:07 ` Danny Milosavljevic
2021-01-08 16:15 ` Jan Nieuwenhuizen
2021-01-08 18:56 ` Danny Milosavljevic
2021-01-08 21:11 ` Danny Milosavljevic
2021-01-08 22:13 ` Jan Nieuwenhuizen
2021-01-08 7:16 ` [Tinycc-devel] " grischka
2021-01-08 13:25 ` Danny Milosavljevic
2021-01-08 13:36 ` [bootstrappable] Re: [Tinycc-devel] " Orians, Jeremiah (DTMB)
2021-01-08 15:16 ` [Tinycc-devel] [bootstrappable] " Vincent Lefevre
2021-01-08 16:12 ` [Tinycc-devel] [bootstrappable] " Jan Nieuwenhuizen
2021-01-25 22:47 ` ARM Unified Assembly Language - GNU as does some weird stuff Danny Milosavljevic
2021-01-25 23:12 ` [bootstrappable] " Orians, Jeremiah (DTMB)
2021-01-26 1:14 ` Danny Milosavljevic
2021-01-08 0:29 ` wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello' Jan Wielkiewicz
2021-01-20 20:19 ` Timothy Sample
2021-01-25 18:48 ` Efraim Flashner
2021-01-29 7:23 ` [bootstrappable] " Jan Nieuwenhuizen
2021-01-29 10:18 ` andrius--- via Development of GNU Guix and the GNU System distribution.
2021-01-29 16:02 ` Orians, Jeremiah (DTMB)
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7n1npr7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=OriansJ@michigan.gov \
--cc=andrius@stikonas.eu \
--cc=bootstrappable@freelists.org \
--cc=guix-devel@gnu.org \
--cc=jeremiah@pdp10.guru \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).