From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kei Kebreau Subject: Re: =?utf-8?B?4oCYc3RhZ2luZ+KAmQ==?= branch Date: Thu, 21 Sep 2017 09:49:50 -0400 Message-ID: <87d16ktb41.fsf@posteo.net> References: <87o9q756qo.fsf@gnu.org> <874lrxb43x.fsf@fastmail.com> <87lgl8u9eu.fsf@posteo.net> <87h8vwtgnp.fsf@posteo.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37255) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dv1rg-0008CW-OU for guix-devel@gnu.org; Thu, 21 Sep 2017 09:50:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dv1ra-0007At-Vw for guix-devel@gnu.org; Thu, 21 Sep 2017 09:50:04 -0400 Received: from mout02.posteo.de ([185.67.36.66]:42794) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dv1ra-000791-PE for guix-devel@gnu.org; Thu, 21 Sep 2017 09:49:58 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id B4BD821068 for ; Thu, 21 Sep 2017 15:49:54 +0200 (CEST) In-Reply-To: <87h8vwtgnp.fsf@posteo.net> (Kei Kebreau's message of "Thu, 21 Sep 2017 07:50:02 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Marius Bakke Cc: guix-devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Kei Kebreau writes: > Kei Kebreau writes: > >> Marius Bakke writes: >> >>> Ludovic Court=C3=A8s writes: >>> >>>> Hello! >>>> >>>> Marius, what=E2=80=99s the status of =E2=80=98staging=E2=80=99? (Sorr= y 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=E2=80=99t 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. Pushed to staging as dc1d3cdef70f0e3c047c229c2a0e561d1f47bde8. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEg7ZwOtzKO2lLzi2m5qXuPBlGeg0FAlnDw38ACgkQ5qXuPBlG eg0hjxAAowHpVGp3hEz/zNAbhTl+tWRiiTP85pUG2hocthBq7S+N6I4VNL5gKU4y BiUb+8vdgKx9f7cjecbRxl6muUX4v3Ph5/+jlm15a9XO1Xaj0zGZtPWEAzsO5Ffc nJ5PgPdexigCpsVqsf2u11Mr7z8WrdAiQ0yx6xC12qhanb9u6OC96HxFptCeyVub CzO5BhMHWMNw4ZA1JAtFtvdGhZW9fGdauRiY1u6JtLncRk38UiPLpKGNQjSQzrPG ZPGJu01GOTACdKQJAow1XnZIoNIAodCqCcJNkWdtYptk2zH8kbBsK0mxuqDP3Ehp N+yFJs7LI4ejy5OqFHEkjHX4F8SCP4Xm7+e/caZ4QLhVjY2/LdAUX+6P91Mj3nJW NzrJWZcsZB2xHhxAxKqo3jM1JNxxxhrBmtHmYUQHY/YOH3r3ljUMXCzwVowPgQwn gRBOe80ZGr/iApocvGyEIKZRrz9gX4nyvJCFhzgt1jtuECV4ia1qRxS6703Jr6sR 5OOV0XJjs4G+gZ/C5TEwO4HbR7TDcB0VrDAmUzsfvRuyO1s33a9mcTOLKt8+/P/5 D0I7iLwJN3x4ZoBTPpBPuMHyVXyHSs/YQd2wsNkvKsp6JYZFO65j5o6Usg5eoDMA obPC5ezbtj3Y5SrlRxf7fMcYi2DxzF0+RXmN30lXdc/5ApUgkyQ= =ebtF -----END PGP SIGNATURE----- --=-=-=--