From: Marius Bakke <mbakke@fastmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: guix-devel@gnu.org
Subject: Re: Let's merge staging!
Date: Sun, 26 May 2019 08:31:36 +0200 [thread overview]
Message-ID: <87r28ld8vr.fsf@devup.no> (raw)
In-Reply-To: <cu7tvdimmdl.fsf@systemreboot.net>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
Arun Isaac <arunisaac@systemreboot.net> writes:
>> Anything missing before the freeze?
>
> I closed issue 32102 and pushed a patch to core-updates-next back in
> November 2018, but it seems to have been lost somehow. It's still not in
> master. Can we include it now in staging?
>
> https://issues.guix.info/issue/32102
These commits are on the current 'core-updates' branch as of 89e7f90d.
Changing python-build-system entails many more rebuilds than 'staging'
usually handles. I'd rather not include it this round because that
would probably double the amount of builds and thus time to merge.
Let's focus on getting the 'core-updates' branch in shape instead. It
is long overdue by now...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-05-26 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 11:06 Let's merge staging! Marius Bakke
2019-05-25 18:15 ` Arun Isaac
2019-05-26 6:31 ` Marius Bakke [this message]
2019-05-26 18:55 ` Arun Isaac
2019-05-28 15:08 ` Ludovic Courtès
2019-06-03 15:10 ` Marius Bakke
2019-06-03 17:02 ` Pierre Neidhardt
2019-06-03 18:10 ` Marius Bakke
2019-06-03 18:31 ` Pierre Neidhardt
2019-06-03 18:44 ` Marius Bakke
2019-06-05 14:13 ` 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=87r28ld8vr.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@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).