unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Alexandros Theodotou <alex@zrythm.org>, 38163@debbugs.gnu.org
Subject: bug#38163: GDK does not return the monitor's refresh rate
Date: Sat, 16 Nov 2019 16:07:34 +0100	[thread overview]
Message-ID: <871ru7zwp5.fsf@gnu.org> (raw)
In-Reply-To: <87tv75f16b.fsf@devup.no> (Marius Bakke's message of "Fri, 15 Nov 2019 19:24:12 +0100")

Hi,

Marius Bakke <mbakke@fastmail.com> skribis:

> Alexandros Theodotou <alex@zrythm.org> writes:
>
>> Hi Ludo,
>>
>>> We won’t make this change in ‘master’ because it entails too many
>>> rebuilds, but it could go on the next branch for massive rebuilds. 
>>
>> Makes sense. I will be using my local gtk+ version for a while then
>> until this change goes live.
>
> Note that this change is already in the staging branch since commit
> 52b61e999101724c7e2d341586e9a6150614f208.

Nice! I wasn’t aware of it.

> Unfortunately the branch has gone stale due to some Qt/qmake plugin
> issues & I haven't had time to work on it.  I will try to find a
> workaround this weekend, if nothing else, as only a handful packages are
> affected.

Let’s motivate each other on IRC over the week-end.  I’d be happy to
give a hand to get that branch merged!

Thanks,
Ludo’.

  reply	other threads:[~2019-11-16 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 16:44 bug#38163: GDK does not return the monitor's refresh rate Alexandros Theodotou
2019-11-11 20:53 ` Ludovic Courtès
2019-11-11 21:31   ` Alexandros Theodotou
2019-11-13 20:56     ` Bengt Richter
2019-11-14 21:00       ` Ludovic Courtès
2019-11-15 18:24     ` Marius Bakke
2019-11-16 15:07       ` Ludovic Courtès [this message]
2020-05-27  0:10 ` Alexandros Theodotou

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=871ru7zwp5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38163@debbugs.gnu.org \
    --cc=alex@zrythm.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).