unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: "andrés ramírez" <rrandresf@hotmail.com>, 57364@debbugs.gnu.org
Subject: bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY
Date: Tue, 27 Sep 2022 14:49:12 +0200	[thread overview]
Message-ID: <87v8p92d9z.fsf_-_@gnus.org> (raw)
In-Reply-To: <878rn6oxhs.fsf@yahoo.com> (Po Lu's message of "Tue, 30 Aug 2022 18:07:43 +0800")

Po Lu <luangruo@yahoo.com> writes:

>> Are You going to apply the patch?
>
> No.  It is too large for the release branch.

Skimming this bug report, the conclusion seems to be that it's fixed on
the "master" branch, but it's too large to backport to Emacs 28 (and in
any case, it's somewhat doubtful there will be further Emacs 28
releases), so I'm closing this bug report.





  reply	other threads:[~2022-09-27 12:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 17:51 bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY Andrés Ramírez
2022-08-24  1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-25 14:29   ` andrés ramírez
2022-08-25 15:13   ` andrés ramírez
2022-08-26  1:07     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26  1:50       ` andrés ramírez
2022-08-26  3:08         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26  3:43           ` andrés ramírez
2022-08-26  5:44             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 13:59               ` andrés ramírez
2022-08-27  1:17                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-29 19:58                   ` andrés ramírez
2022-08-30  1:19                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30  5:28                       ` andrés ramírez
2022-08-30  7:02                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-30  7:29                           ` bug#57364: [PATCH] (was: bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY) andrés ramírez
2022-08-30 10:07                             ` bug#57364: [PATCH] Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-27 12:49                               ` Lars Ingebrigtsen [this message]
2022-09-27 13:46                                 ` bug#57364: 28.1.91; asynchronous X server error when creating a second frame on alternate DISPLAY andrés ramírez
2022-09-27 17:32                                   ` Lars Ingebrigtsen
2022-08-30  8:02 ` bug#57364: 28.1; emacs segfaulted when debugging emacs form within emacs for bug#57364 Andrés Ramírez

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8p92d9z.fsf_-_@gnus.org \
    --to=larsi@gnus.org \
    --cc=57364@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=rrandresf@hotmail.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/emacs.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).