From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: ulm@gentoo.org, 68842@debbugs.gnu.org
Subject: bug#68842: 29.2; implicit declaration of function 'XOpenDisplay'
Date: Thu, 01 Feb 2024 09:38:24 +0200 [thread overview]
Message-ID: <86eddw1vnz.fsf@gnu.org> (raw)
In-Reply-To: <87plxhndzo.fsf@yahoo.com> (message from Po Lu on Thu, 01 Feb 2024 09:56:59 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Ulrich Müller <ulm@gentoo.org>, 68842@debbugs.gnu.org
> Date: Thu, 01 Feb 2024 09:56:59 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Po Lu, any comments to the patch?
> >
> > I don't mind installing this on emacs-29, if it's TRT, but the chances
> > for us to have another Emacs 29.x release are slim at best at this
> > point. So I wonder whether you should bother.
>
> I suggest cherry-picking 6c1413d5ef0d1fea639b0d8c83a0c0065d99359b
> instead, because the systems where this flag is required have lapsed out
> of existence. It can't hurt.
That's not something we do on release branches -- they aren't supposed
to remove platforms or configurations.
So I'd prefer not to do that. Is the original patch suggested by
Ulrich problematic in some way? I understand that removing the text
is easier, but assuming we don't want to drop support for GCC 4.6 on
the release branch, do you see any problem in installing the patch
Ulrich posted?
next prev parent reply other threads:[~2024-02-01 7:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 8:03 bug#68842: 29.2; implicit declaration of function 'XOpenDisplay' Ulrich Müller
2024-01-31 17:26 ` Eli Zaretskii
2024-01-31 19:16 ` Ulrich Mueller
2024-01-31 19:32 ` Eli Zaretskii
2024-02-01 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-01 7:38 ` Eli Zaretskii [this message]
2024-02-01 8:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-01 8:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-01 9:03 ` Eli Zaretskii
2024-02-01 9:21 ` Ulrich Mueller
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=86eddw1vnz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68842@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=ulm@gentoo.org \
/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.