From: Marius Bakke <mbakke@fastmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org, 38390@debbugs.gnu.org
Subject: [bug#38390] Starting 'core-updates'?
Date: Fri, 14 Feb 2020 16:18:50 +0100 [thread overview]
Message-ID: <87eeux8aed.fsf@devup.no> (raw)
In-Reply-To: <87wo8qcy7o.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Jan Nieuwenhuizen <janneke@gnu.org> writes:
> Marius Bakke writes:
>
> Hello Marius,
>
>> The 'core-updates' branch is starting to look pretty good, and I am
>> happy to report that it "works for me". :-)
>>
>> Some of the big changes include:
>
>> I suggest that we set a "freeze" date shortly after FOSDEM to start
>> integrating it. Are there other branches that should be included?
>
>> Maybe wip-bootstrap
>
> Definately maybe! I think that Timothy, Ludo and I have finally done
> what set out to do (see https://bugs.gnu.org/38390).
>
> I have squashed the remaining squash-commits and freshly rebased
> `wip-bootstrap' on core-updates, so I think that from our point of view
> we are ready for merge. WYDT?
Excellent, really looking forward to seeing this merged! Cutting the
bootstrap seed down to ~60 MiB is nothing short of amazing.
I think that with this branch merged as well as the glibc&binutils
update from <https://issues.guix.gnu.org/issue/39456> we are ready to
start the 'core-updates' branch. \o/
We still need to change the default Guile to 3.0. Any takers? :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-02-14 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mua8sma4.fsf@devup.no>
2020-02-13 15:18 ` [bug#38390] Starting 'core-updates'? Jan Nieuwenhuizen
2020-02-14 15:18 ` Marius Bakke [this message]
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=87eeux8aed.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=38390@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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).