From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 28189@debbugs.gnu.org
Subject: bug#28189: 26.0.50; Emacs uses deprecated function gtk_window_parse_geometry
Date: Sat, 23 Sep 2017 19:48:30 +0300 [thread overview]
Message-ID: <83r2ux9x9d.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkQD_4uCEv3He5eCi_9Yf892jeZ=KbBPu+jxOp=BRP6D3w@mail.gmail.com> (message from Philipp Stephani on Sat, 23 Sep 2017 16:32:54 +0000)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sat, 23 Sep 2017 16:32:54 +0000
> Cc: 28189@debbugs.gnu.org
>
> Actually, the fix should have been pushed to the release branch to
> begin with, since this bug is on the list of Emacs 26.1 release
> blockers.
>
> I'm not sure to what extent these patches should be called "fixes": Sure, they get rid of warnings, but generally
> only by no longer calling the "offending" functions, without much testing whether anything might be broken.
Emacs 26.1 didn't even see its first pretest. There's ample time to
test these changes until the release.
I'm also okay with removing the bug from the list of blockers, if
that's what you recommend.
next prev parent reply other threads:[~2017-09-23 16:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 20:22 bug#28189: 26.0.50; Emacs uses deprecated function gtk_window_parse_geometry Philipp
2017-08-23 8:46 ` martin rudalics
2017-08-23 10:38 ` Philipp Stephani
2017-08-23 13:19 ` martin rudalics
2017-08-23 23:26 ` Philipp Stephani
2017-08-24 9:37 ` martin rudalics
2017-08-25 9:28 ` Philipp Stephani
2017-08-26 9:29 ` martin rudalics
2017-08-27 13:34 ` Philipp Stephani
2017-09-03 11:49 ` martin rudalics
2017-09-19 15:35 ` Philipp Stephani
2017-09-19 16:38 ` Philipp Stephani
2017-09-23 11:22 ` Philipp Stephani
2017-09-23 13:21 ` martin rudalics
2017-09-23 13:28 ` Eli Zaretskii
2017-09-23 16:32 ` Philipp Stephani
2017-09-23 16:48 ` Eli Zaretskii [this message]
2017-09-23 18:28 ` martin rudalics
2017-09-23 18:31 ` Eli Zaretskii
2017-09-23 16:36 ` Philipp Stephani
2017-09-23 18:29 ` martin rudalics
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=83r2ux9x9d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28189@debbugs.gnu.org \
--cc=p.stephani2@gmail.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/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.