From: Marius Bakke <mbakke@fastmail.com>
To: "Kei Kebreau" <kkebreau@posteo.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 'core-updates' Q4 2019
Date: Tue, 15 Oct 2019 18:49:53 +0200 [thread overview]
Message-ID: <87tv8a0x8u.fsf@devup.no> (raw)
In-Reply-To: <874l0ag5kv.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
Kei Kebreau <kkebreau@posteo.net> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hello Kei,
>>
>> Kei Kebreau <kkebreau@posteo.net> skribis:
>>
>>> I have the GNOME 3.32 branch! I'm building it on top of the new
>>> core-updates as you read this message. If everything still builds, I'll
>>> immediately send my changes to the guix-patches mailing list for review
>>> and testing.
>>
>> Shouldn’t you instead base it on ‘master’ or ‘staging’?
>>
>> That may allow us to merge it more quickly, especially if these are only
>> GNOME-related changes.
>>
>> Thanks for working on it!
>>
>> Ludo’.
>
> Hi Ludovic,
>
> Taken individually, most changes on the GNOME 3.32 branch could be
> pushed to master without too much trouble. The only issues are big changes like
> upgrading Vala. The following changes would cause a large number of
> rebuilds:
>
> At least 300 rebuilds: python-pygobject, gtk+
>
> At least 1200 rebuilds: gtk-doc, vala, yelp-tools, python-parameterized,
> python-check-manifest, python-anytree
>
> I'll minimize the changes, isolate what I can, and submit the results
> for review as time allows!
Thanks! Sounds like something we can handle in a 'staging' cycle.
By the way, GNOME 3.34 is out, and 3.36 is slated for March. So I think
we will finally be able to catch up with GNOME again soon...
(let's focus on 3.32 first though ;-))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-15 16:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 21:55 'core-updates' Q4 2019 Marius Bakke
2019-10-09 11:53 ` Mathieu Othacehe
2019-10-10 14:32 ` Ludovic Courtès
2019-10-10 15:35 ` Mathieu Othacehe
2019-10-10 21:22 ` Svante Signell
2019-10-11 7:52 ` Ludovic Courtès
2019-10-11 20:42 ` Kei Kebreau
2019-10-12 22:15 ` Ludovic Courtès
2019-10-15 1:28 ` Kei Kebreau
2019-10-15 16:49 ` Marius Bakke [this message]
2019-10-17 20:44 ` Kei Kebreau
2019-10-17 21:29 ` Ricardo Wurmus
2019-10-18 1:53 ` Kei Kebreau
2019-10-18 3:08 ` Ricardo Wurmus
2019-10-19 13:34 ` Timothy Sample
2019-10-20 3:29 ` Kei Kebreau
2019-10-21 13:58 ` pelzflorian (Florian Pelz)
2019-10-22 0:37 ` Timothy Sample
2019-10-23 3:07 ` Timothy Sample
2019-10-23 7:49 ` pelzflorian (Florian Pelz)
2019-10-26 20:26 ` Kei Kebreau
2019-10-23 17:49 ` Marius Bakke
2019-10-24 2:07 ` Timothy Sample
2019-10-24 18:17 ` Marius Bakke
2019-10-26 21:25 ` Timothy Sample
2019-11-02 2:27 ` Kei Kebreau
2019-11-04 19:37 ` Miguel Arruga Vivas
2019-11-05 23:38 ` Kei Kebreau
2019-11-06 17:46 ` Leo Famulari
2019-11-07 1:16 ` Kei Kebreau
2019-11-07 2:58 ` Timothy Sample
2019-11-08 0:58 ` Miguel Arruga Vivas
2019-11-23 2:11 ` Kei Kebreau
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv8a0x8u.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=kkebreau@posteo.net \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.