all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: Joost Kremers <joostkremers@fastmail.fm>, Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 69454@debbugs.gnu.org, eric.marsden@risk-engineering.org
Subject: bug#69454: Not possible to insert an empty vtable
Date: Sun, 2 Jun 2024 12:49:52 -0500	[thread overview]
Message-ID: <debafde7-1fd0-482b-bb1a-75ab816e4d5b@alphapapa.net> (raw)
In-Reply-To: <861q5i4gk6.fsf@fastmail.fm>

On 5/31/24 01:54, Joost Kremers wrote:

> I haven't updated the documentation yet nor did I add a NEWS entry, because I
> first wanted to make sure you agree with the direction of this patch: Adam
> suggested empty vtables should not be allowed, but this patch explicitly allows
> them.

IIRC I only suggested that because it would mean fewer changes to the 
code, but if you've already written code to allow it, I don't object.  :)

Thanks for working on these issues.





  reply	other threads:[~2024-06-02 17:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28 14:29 bug#69454: Not possible to insert an empty vtable Eric Marsden
2024-03-09  8:54 ` Eli Zaretskii
2024-03-11 19:57   ` Adam Porter
2024-03-14  9:37     ` Eli Zaretskii
2024-03-16  0:14       ` Adam Porter
2024-04-30  9:10   ` Joost Kremers
2024-04-30 12:14     ` Eli Zaretskii
     [not found]       ` <8f5fb814-5d88-4ad3-b12a-8246325d5d21@alphapapa.net>
2024-05-01 11:54         ` Eli Zaretskii
2024-05-02  7:31         ` Joost Kremers
2024-05-05 12:15     ` Joost Kremers
2024-05-30 21:40       ` Joost Kremers
2024-05-30 21:52         ` Joost Kremers
2024-05-31  5:24           ` Eli Zaretskii
2024-05-31  6:54             ` Joost Kremers
2024-06-02 17:49               ` Adam Porter [this message]
2024-06-03 12:13                 ` Joost Kremers
2024-06-08 12:34                   ` Eli Zaretskii

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=debafde7-1fd0-482b-bb1a-75ab816e4d5b@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=69454@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=eric.marsden@risk-engineering.org \
    --cc=joostkremers@fastmail.fm \
    --cc=larsi@gnus.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.