From: Kei Kebreau <kkebreau@posteo.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: ‘staging’ branch
Date: Thu, 21 Sep 2017 07:50:02 -0400 [thread overview]
Message-ID: <87h8vwtgnp.fsf@posteo.net> (raw)
In-Reply-To: <87lgl8u9eu.fsf@posteo.net> (Kei Kebreau's message of "Wed, 20 Sep 2017 21:28:57 -0400")
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
Kei Kebreau <kkebreau@posteo.net> writes:
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Hello!
>>>
>>> Marius, what’s the status of ‘staging’? (Sorry I had to pick someone as
>>> the staging master, so to speak. :-))
>>
>> I've shepherded the last few iterations, so I guess it's only fair!
>>
>> I was waiting for Keis "monster" patch from #27898, but if we are to
>> merge this before 'core-updates' we'll have to start building it now.
>>
>> Tangentially, there's also the Python 3.6 update. Maybe we can just
>> toss it at 'core-updates', WDYT?
>>
>> @Kei: Feel free to push the patch to 'staging' if you can. If it
>> doesn't make it until tomorrow, it will probably have to wait until the
>> next 'core-updates' is merged :/
>>
>
> I've updated and attached the patch over the past few hours. I haven't
> tested by building each affected package, so I'm not sure whether it's
> okay to push.
>
>>> Wouldn’t it be nice to merge master in staging, and then merge staging
>>> real soon?
>>
>> I've done the first part. Will start it tomorrow, unless there are
>> objections.
Barring any objections, I'll be pushing in about an hour.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-09-21 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 10:21 ‘staging’ branch Ludovic Courtès
2017-09-20 18:46 ` Marius Bakke
2017-09-21 1:28 ` Kei Kebreau
2017-09-21 2:31 ` Ben Woodcroft
2017-09-21 11:26 ` Ben Woodcroft
2017-09-21 11:50 ` Kei Kebreau [this message]
2017-09-21 13:49 ` Kei Kebreau
2017-09-21 19:27 ` Marius Bakke
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=87h8vwtgnp.fsf@posteo.net \
--to=kkebreau@posteo.net \
--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 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).