From: Kei Kebreau <kkebreau@posteo.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Shall we merge wip-gnome3.30 to core-updates?
Date: Wed, 19 Jun 2019 16:22:26 -0400 [thread overview]
Message-ID: <87pnn9iav1.fsf@posteo.net> (raw)
In-Reply-To: <87tvcpppyr.fsf@posteo.net> (Kei Kebreau's message of "Sun, 16 Jun 2019 10:25:16 -0400")
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Kei Kebreau <kkebreau@posteo.net> writes:
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> @Kei: If you have tested this branch elsewhere, I think it's okay to
>> merge even if it does not yet build on 'core-updates'.
>
> Great! I'll give the branch a test on top of "master" first.
Update on the GNOME updates: while most things seem to be working as they
were before, others may be off in subtle ways. For example, the time
display is UTC and seemingly unchangeable.
This could be partly caused by the fact that only some of the GNOME
packages were updated to their 3.30 versions, but I don't know how GNOME
works well enough to diagnose the issue right away.
If this is okay, I can push the updates tomorrow.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-06-19 20:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 15:33 Shall we merge wip-gnome3.30 to core-updates? Kei Kebreau
2019-06-08 20:30 ` Marius Bakke
2019-06-10 9:32 ` Ludovic Courtès
2019-06-16 9:21 ` 'core-updates' summer 2019 Marius Bakke
2019-06-16 21:43 ` Mark H Weaver
2019-06-17 10:01 ` Ludovic Courtès
2019-06-13 23:09 ` Shall we merge wip-gnome3.30 to core-updates? Kei Kebreau
2019-06-16 8:59 ` Efraim Flashner
2019-06-16 9:11 ` Marius Bakke
2019-06-16 14:25 ` Kei Kebreau
2019-06-19 20:22 ` Kei Kebreau [this message]
2019-06-19 21:49 ` Ricardo Wurmus
2019-06-21 5:10 ` 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=87pnn9iav1.fsf@posteo.net \
--to=kkebreau@posteo.net \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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).