From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31223@debbugs.gnu.org, tbading@web.de
Subject: bug#31223: [PATCH] Fix empty/incorrect GTK menus on HiDPI monitors with window scaling factor > 1
Date: Tue, 03 Dec 2019 09:22:16 +0100 [thread overview]
Message-ID: <m2o8wpsts7.fsf@gmail.com> (raw)
In-Reply-To: <vu7c70k1t285s5.fsf@chaotikum.eu>
>>>>> On Mon, 02 Dec 2019 17:53:16 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Date: Mon, 02 Dec 2019 11:35:03 +0100
>> Cc: 31223@debbugs.gnu.org
>>
>> Do you have an Emacs copyright assignment on file?
Eli> No, not AFAICT.
>> If not, Eli, is the patch small enough to apply without an
>> assignment?
Eli> Yes.
OK, pushed as a05bafffdc , with some minor changes to the commit
message.
Iʼll leave the bug open until I get a chance to verify the
multi-monitor cases.
Robert
next prev parent reply other threads:[~2019-12-03 8:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 11:40 bug#31223: 25.3; New menus are empty with GTK3 Thomas Schneider
[not found] ` <handler.31223.B.15242361664927.ack@debbugs.gnu.org>
2018-05-01 16:16 ` Thomas Schneider
2018-05-01 16:48 ` Eli Zaretskii
2018-05-01 17:01 ` Thomas Schneider
2018-05-01 17:08 ` Eli Zaretskii
2018-05-01 17:20 ` Thomas Schneider
2018-05-01 18:43 ` Eli Zaretskii
2018-05-03 8:36 ` Thomas Schneider
2018-05-03 17:52 ` Eli Zaretskii
2018-07-20 22:44 ` Noam Postavsky
2018-05-01 23:18 ` Noam Postavsky
2019-11-27 16:03 ` bug#31223: [PATCH] Fix empty/incorrect GTK menus on HiDPI monitors with window scaling factor > 1 Tobias Bading
2019-11-28 8:20 ` Robert Pluim
2019-11-28 9:32 ` Tobias Bading
2019-11-28 9:44 ` Robert Pluim
2019-12-02 10:35 ` Robert Pluim
2019-12-02 15:53 ` Eli Zaretskii
2019-12-03 8:22 ` Robert Pluim [this message]
2019-12-17 14:43 ` Robert Pluim
2020-01-07 16:15 ` Robert Pluim
2020-01-07 16:22 ` Eli Zaretskii
2020-01-07 16:31 ` Robert Pluim
2019-11-28 12:04 ` Noam Postavsky
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=m2o8wpsts7.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=31223@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tbading@web.de \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.