From: Timothy Sample <samplet@ngyro.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 38390@debbugs.gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: [bug#38390] [core-updates] Scheme-only bootstrap: merge wip-bootstrap
Date: Sun, 15 Dec 2019 17:39:28 -0500 [thread overview]
Message-ID: <87zhftgqn3.fsf@ngyro.com> (raw)
In-Reply-To: <87o8w9s284.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 15 Dec 2019 22:33:47 +0100")
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> Jan Nieuwenhuizen <janneke@gnu.org> skribis:
>
>> We are really getting there! I would like to do a rewrite once Gash
>> 0.2.0 is out. What to do about Gash Core Utils? I also plan to do a
>> rewrite once MES 0.22 is out.
>
> I think we should probably wait for the Gash and Gash Core Utils
> releases so we can refer to them directly. How does that sound to you,
> Timothy?
I’m planning on releasing Gash tonight, so that should be okay. :D
For the utilities, it might take some time (especially since we are
running up against the holidays). My current plan is to do it as
quickly as possible, meaning that I will focus on the bare minimum for a
first release. Even then, it won’t be speedy: besides cleaning up
what’s there and setting up the build scripts, I will have to coordinate
with the folks at Savannah to get another Git repo.
Even if it takes a few weeks for a release, I think it makes sense to
wait. This whole project has taken years! What’s a couple of weeks?
:)
-- Tim
next prev parent reply other threads:[~2019-12-15 22:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 16:38 [bug#38390] [core-updates] Scheme-only bootstrap: merge wip-bootstrap Jan Nieuwenhuizen
2019-12-01 14:01 ` Ludovic Courtès
2019-12-01 16:25 ` Timothy Sample
2019-12-01 16:55 ` Jan Nieuwenhuizen
2019-12-01 17:14 ` Ludovic Courtès
2019-12-01 17:21 ` Jan Nieuwenhuizen
2019-12-06 6:53 ` Jan Nieuwenhuizen
2019-12-07 22:31 ` Ludovic Courtès
2019-12-11 18:25 ` Jan Nieuwenhuizen
2019-12-15 21:33 ` Ludovic Courtès
2019-12-15 22:39 ` Timothy Sample [this message]
2019-12-15 22:45 ` Brett Gilio
2019-12-16 6:34 ` Jan Nieuwenhuizen
2019-12-16 19:28 ` Jan Nieuwenhuizen
2019-12-18 22:55 ` Jan Nieuwenhuizen
2019-12-19 11:08 ` Ludovic Courtès
2020-02-03 17:37 ` [bug#38390] [bug #38390] Building bootstrap Gash and Gash-Utils Timothy Sample
2020-02-05 8:58 ` Ludovic Courtès
2020-02-05 14:32 ` Timothy Sample
2020-02-05 21:33 ` Ludovic Courtès
2020-02-06 22:58 ` Jan Nieuwenhuizen
2020-02-07 11:00 ` Ludovic Courtès
2020-02-08 17:33 ` Timothy Sample
2020-02-08 22:32 ` Jan Nieuwenhuizen
2020-02-10 2:23 ` Timothy Sample
2020-02-11 13:56 ` Ludovic Courtès
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=87zhftgqn3.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=38390@debbugs.gnu.org \
--cc=janneke@gnu.org \
--cc=ludo@gnu.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.
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).