From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Arun Isaac" <arunisaac@systemreboot.net>
Cc: Ricardo Wurmus <rekado@elephly.net>, 29745@debbugs.gnu.org
Subject: [bug#29745] [PATCH 0/3] Disallow phase returning <unspecified>.
Date: Sun, 17 Dec 2017 19:14:42 +0100 [thread overview]
Message-ID: <87fu896x2l.fsf@fastmail.com> (raw)
In-Reply-To: <87efnt9tvw.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> However, ‘core-updates’ is supposedly frozen right now (I’m Cc’ing
> Marius who is the de facto ‘core-updates’ manager :-)). So perhaps we
> should hold on until the next ‘core-updates’ is open.
>
> What do people think?
Many are already working on it and full-rebuilds are annoying. So I
would prefer waiting until the next window.
But there are a few problems with core-updates still, so technically
there is a chance a full rebuild is necessary. Maybe fork off
core-updates to core-updates-next so they are available?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2017-12-17 18:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 23:12 [bug#29745] [PATCH 0/3] Disallow phase returning <unspecified> Arun Isaac
2017-12-16 23:16 ` [bug#29745] [PATCH 1/3] build: gnu-build-system: " Arun Isaac
2017-12-16 23:16 ` [bug#29745] [PATCH 2/3] build: gnu-build-system: Return #t from phases Arun Isaac
2017-12-16 23:16 ` [bug#29745] [PATCH 3/3] gnu: " Arun Isaac
2017-12-17 6:27 ` [bug#29745] [PATCH 0/3] Disallow phase returning <unspecified> Ricardo Wurmus
2017-12-17 16:55 ` Ludovic Courtès
2017-12-17 17:47 ` Arun Isaac
2017-12-18 8:01 ` Ludovic Courtès
2017-12-18 8:44 ` Ricardo Wurmus
2017-12-28 11:43 ` bug#29745: " Arun Isaac
2017-12-18 9:06 ` [bug#29745] " Arun Isaac
2017-12-19 8:38 ` Ludovic Courtès
2017-12-19 21:58 ` Mark H Weaver
2017-12-18 9:26 ` Andreas Enge
2017-12-17 18:14 ` 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=87fu896x2l.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=29745@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
/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).