unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <marius@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>, guix-devel@gnu.org
Subject: Re: staging freeze
Date: Wed, 14 Oct 2020 00:28:59 +0200	[thread overview]
Message-ID: <871ri1rc9g.fsf@gnu.org> (raw)
In-Reply-To: <A7173A33-7218-4E1E-9FE1-B0EAC7C93F1A@lepiller.eu>

[-- Attachment #1: Type: text/plain, Size: 640 bytes --]

Julien Lepiller <julien@lepiller.eu> writes:

> Le 13 octobre 2020 17:54:16 GMT-04:00, Marius Bakke <marius@gnu.org> a écrit :
>>Hello Guix,
>>
>>I've pushed a set of updates to the long-overdue "staging" branch.
>>
>>Let's get it merged once Cuirass is done building for the various
>>architectures.  Not sure how long that takes now that we no longer use
>>transparent QEMU emulation for AArch64 and armhf.
>
> I have my groovy update ready to push to staging. Can I push it, or should I wait for next time staging is open?

Sure, go ahead!  I suppose we can give people a day or two to brush up
any almost-ready patches.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

  reply	other threads:[~2020-10-13 22:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 21:54 staging freeze Marius Bakke
2020-10-13 21:57 ` Julien Lepiller
2020-10-13 22:28   ` Marius Bakke [this message]
2020-10-15 12:33 ` zimoun
  -- strict thread matches above, loose matches on Subject: below --
2016-12-23  5:23 Staging freeze Leo Famulari
2016-12-23  6:00 ` John Darrington
2016-12-26 18:16   ` Leo Famulari
2016-12-27 23:56 ` Leo Famulari
2016-12-28  4:13   ` Leo Famulari
2016-12-28  9:17     ` John Darrington
2016-12-29 17:16       ` Leo Famulari
2016-12-29 17:51       ` Ludovic Courtès
2016-12-29 18:42         ` Leo Famulari
2016-12-31 11:12           ` Ludovic Courtès
2017-01-04  8:45 ` Leo Famulari
2017-01-04 22:31   ` 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=871ri1rc9g.fsf@gnu.org \
    --to=marius@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    /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).