From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Starting 'core-updates'?
Date: Tue, 28 Jan 2020 11:51:01 +0100 [thread overview]
Message-ID: <87mua7hn1m.fsf@gnu.org> (raw)
In-Reply-To: <87mua8sma4.fsf@devup.no> (Marius Bakke's message of "Mon, 27 Jan 2020 20:59:47 +0100")
Hi!
Marius Bakke <mbakke@fastmail.com> skribis:
> 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 or GNOME 3.34?
Is ‘default-guile’ pointing to Guile 3.0 there? We should do that,
though perhaps a 3.0.1 would be welcome.
Besides I’d like to merge ’wip-build-systems-gexp’ one day, but I
haven’t touched it in a long time and there’s potential for breakage.
Dunno if this should wait some more…
Anyhow, thanks for getting the ball rolling!
Ludo’.
next prev parent reply other threads:[~2020-01-28 10:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 19:59 Starting 'core-updates'? Marius Bakke
2020-01-27 20:44 ` Pierre Neidhardt
2020-01-27 21:46 ` zimoun
2020-01-28 8:55 ` Mathieu Othacehe
2020-01-28 9:08 ` Christopher Baines
2020-01-28 10:47 ` Ludovic Courtès
2020-01-28 10:51 ` Ludovic Courtès [this message]
2020-01-31 19:48 ` Maxim Cournoyer
2020-02-13 15:18 ` Jan Nieuwenhuizen
2020-02-13 15:18 ` [bug#38390] " Jan Nieuwenhuizen
2020-02-14 15:18 ` Marius Bakke
2020-02-14 15:18 ` [bug#38390] " Marius Bakke
2020-02-18 6:25 ` [bug#38390] [core-updates] Scheme-only bootstrap: merge wip-bootstrap / Starting `core-updates' Jan Nieuwenhuizen
-- strict thread matches above, loose matches on Subject: below --
2018-04-21 7:54 Successfully running GNOME on core-updates + staging Mark H Weaver
2018-04-22 19:55 ` Ludovic Courtès
2018-04-23 18:13 ` Marius Bakke
2018-04-25 12:14 ` Ludovic Courtès
2018-05-01 14:12 ` Starting 'core-updates' Marius Bakke
2018-05-01 14:23 ` Leo Famulari
2018-05-01 18:23 ` Mark H Weaver
2018-05-01 20:46 ` Ludovic Courtès
2018-05-01 21:21 ` Mark H Weaver
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=87mua7hn1m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.