all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: dick <dick.r.chiang@gmail.com>
To: 56372@debbugs.gnu.org
Cc: luangruo@yahoo.com, larsi@gnus.org
Subject: bug#56372: 29.0.50; [PATCH] Avoid BadMatch X11 error
Date: Mon, 04 Jul 2022 08:12:48 -0400	[thread overview]
Message-ID: <87r131m5z3.fsf@dick> (raw)
In-Reply-To: <87r1319ojr.fsf@yahoo.com> (Po Lu via's message of "Mon, 04 Jul 2022 18:10:00 +0800")

BrfGEtSakote> That piece of code is already inside "if (dpyinfo)" -- in
BrfGEtSakote> fact, your patch misses a use-after-free, which has
BrfGEtSakote> already been fixed on master.

Sheesh, how about "Thanks, I fixed it in bd034b3," as opposed to
implying there was never a bug, and that my patch fails to
address an unrelated issue.

I get it though.  My own social and technical failings in the private
sector have also led me to emacs, a halfway house for greybeards exiled
from the labor market.





  parent reply	other threads:[~2022-07-04 12:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-03 14:45 bug#56372: 29.0.50; [PATCH] Avoid BadMatch X11 error dick.r.chiang
2022-07-04  0:50 ` Katsumi Yamaoka
2022-07-04  5:21   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04 23:15     ` Katsumi Yamaoka
2022-07-04  1:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04  6:05   ` po lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-05  0:21     ` dick
2022-07-05  1:38       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04  4:50 ` dick
2022-07-04 10:10   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04 10:19     ` Lars Ingebrigtsen
2022-07-04 10:58       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-04 12:12     ` dick [this message]
2022-07-04 12:34       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87r131m5z3.fsf@dick \
    --to=dick.r.chiang@gmail.com \
    --cc=56372@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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.