From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Merging staging?
Date: Wed, 09 Jan 2019 22:51:41 +0100 [thread overview]
Message-ID: <8736q11ouq.fsf@gnu.org> (raw)
In-Reply-To: <20181223140048.GE2581@macbook41> (Efraim Flashner's message of "Sun, 23 Dec 2018 16:00:48 +0200")
Hello!
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Thu, Dec 20, 2018 at 03:58:09PM +0100, Julien Lepiller wrote:
>> Hi Guix,
>>
>> I'd like to get staging merged soon, as it wasn't for quite some time. Here
>> are some stats about the current state of substitutes for staging:
>>
>> According to guix weather, we have:
>>
>> | architecture | berlin | hydra |
>> +--------------+--------+-------+
>> | x86_64 | 36.5% | 81.7% |
>> | i686 | 23.8% | 71.0% |
>> | aarch64 | 22.2% | 00.0% |
>> | armhf | 17.0% | 45.6% |
>>
>> What should the next step be?
>>
>
> I have two patches that I should be done with by the end of today, to
> add some more flags to libdrm and mesa for armhf and aarch64. I can hold
> on to it for later, or I can go ahead and push it when it's ready. It
> shouldn't cause any rebuilds on x86_64 or i686.
So what’s the status of this branch now, does anyone know? :-)
Seriously though, we should do something about it.
Ludo’.
next prev parent reply other threads:[~2019-01-09 21:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 14:58 Merging staging? Julien Lepiller
2018-12-20 18:36 ` Mark H Weaver
2018-12-20 22:45 ` Julien Lepiller
2018-12-21 1:17 ` Mark H Weaver
2018-12-21 9:06 ` Gábor Boskovits
2018-12-21 23:06 ` Ludovic Courtès
2018-12-23 14:00 ` Efraim Flashner
2019-01-09 16:27 ` Efraim Flashner
2019-01-09 19:15 ` Mark H Weaver
2019-01-09 19:27 ` Efraim Flashner
2019-01-10 2:27 ` Mark H Weaver
2019-01-10 22:04 ` Ludovic Courtès
2019-01-09 21:51 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-01 8:35 Release v1.4? zimoun
2022-06-03 16:41 ` Ludovic Courtès
2022-06-06 21:17 ` Merging ‘staging’? Ludovic Courtès
2022-06-08 11:50 ` Efraim Flashner
2022-06-08 21:24 ` Ludovic Courtès
2022-06-10 7:57 ` Efraim Flashner
2022-06-11 9:53 ` Ludovic Courtès
2022-06-11 10:49 ` Tom Fitzhenry
2022-06-12 3:58 ` Efraim Flashner
2022-06-12 21:08 ` Ludovic Courtès
2022-06-13 7:03 ` Ludovic Courtès
2022-06-14 4:01 ` Thiago Jung Bauermann
2022-06-09 17:19 ` pelzflorian (Florian Pelz)
2022-06-09 17:41 ` Efraim Flashner
2022-06-09 19:02 ` pelzflorian (Florian Pelz)
2022-06-10 6:07 ` pelzflorian (Florian Pelz)
2022-06-11 7:35 ` pelzflorian (Florian Pelz)
2022-06-12 4:54 ` Thiago Jung Bauermann
2022-06-12 21:06 ` 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=8736q11ouq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--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).