From: Kei Kebreau <kkebreau@posteo.net>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org
Subject: Re: Status of Gnome upgrade?
Date: Thu, 05 Dec 2019 12:35:35 -0500 [thread overview]
Message-ID: <87tv6eoeu0.fsf@posteo.net> (raw)
In-Reply-To: <87lfrqes89.fsf@ngyro.com> (Timothy Sample's message of "Thu, 05 Dec 2019 09:56:22 -0500")
Timothy Sample <samplet@ngyro.com> writes:
> Hi all,
>
> I’ve CC’d Kei who has been looking after this. Thanks Kei!
>
> Brett Gilio <brettg@posteo.net> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Hi Guix,
>>>
>>> does anyone know what’s holding up the Gnome upgrade? It’s sad to see
>>> the upgrade languish when it was almost ready for a merge into master.
>>>
>>> Are there any open issues? Any problems that need solving? I think
>>> this is a high priority item for Guix. I’d love to help getting it
>>> done.
>>>
>>> Any ideas?
>>>
>>> --
>>> Ricardo
>>>
>>>
>>
>> I do not know of any open issues, but I agree with Ricardo fully. This
>> is a high priority issue for Guix that needs to get done sooner rather
>> than later.
>>
>> I am also willing to throw my weight behind it, even though I am not a
>> regular GNOME user.
>
> I’m also willing to help. :)
>
>
> -- Tim
I've been more busy than I'd like over the past few weeks, but I've been
using the "wip-gnome-updates" branch for a while now. Up to November 27
(the "master" branch hasn't been merged into "wip-gnome-updates" since
then), I haven't noticed any regressions in GNOME's functionality. I'd
be delighted to merge "wip-gnome-updates" into "master" and begin work
on GNOME 3.34 updates starting late next week.
next prev parent reply other threads:[~2019-12-05 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 14:02 Status of Gnome upgrade? Ricardo Wurmus
2019-12-05 14:08 ` Brett Gilio
2019-12-05 14:56 ` Timothy Sample
2019-12-05 17:35 ` Kei Kebreau [this message]
2019-12-09 14:50 ` Miguel Arruga Vivas
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=87tv6eoeu0.fsf@posteo.net \
--to=kkebreau@posteo.net \
--cc=guix-devel@gnu.org \
--cc=samplet@ngyro.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 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.