From: Kei Kebreau <kkebreau@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 'core-updates' Q4 2019
Date: Mon, 14 Oct 2019 21:28:32 -0400 [thread overview]
Message-ID: <874l0ag5kv.fsf@posteo.net> (raw)
In-Reply-To: <87ftjxd30v.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 13 Oct 2019 00:15:12 +0200")
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
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,
Kei
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-10-15 1:28 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 [this message]
2019-10-15 16:49 ` Marius Bakke
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
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=874l0ag5kv.fsf@posteo.net \
--to=kkebreau@posteo.net \
--cc=guix-devel@gnu.org \
--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 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).