GNU bug report logs - #69666
[PATCH] (vtable-update-object): Make old-object argument optional

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#69666: closed ([PATCH] (vtable-update-object): Make
 old-object argument optional)
Date: Thu, 21 Mar 2024 10:46:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 21 Mar 2024 12:44:36 +0200
with message-id <8634sj3luz.fsf <at> gnu.org>
and subject line Re: bug#69666: [PATCH] (vtable-update-object): Make old-object argument optional
has caused the debbugs.gnu.org bug report #69666,
regarding [PATCH] (vtable-update-object): Make old-object argument optional
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
69666: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=69666
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Adam Porter <adam <at> alphapapa.net>
To: bug-gnu-emacs <at> gnu.org
Subject: [PATCH] (vtable-update-object): Make old-object argument optional
Date: Fri, 8 Mar 2024 23:51:33 -0600

[Message part 3 (text/plain, inline)]

Hi,

Please see the attached patch which makes `vtable-update-object' easier 
to use in the common case of updating an existing object's 
representation in a table (rather than replacing it with another object).

Thanks,
Adam

[0001-vtable-update-object-Make-old-object-argument-option.patch (text/x-patch, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Adam Porter <adam <at> alphapapa.net>
Cc: 69666-done <at> debbugs.gnu.org
Subject: Re: bug#69666: [PATCH] (vtable-update-object): Make old-object
 argument optional
Date: Thu, 21 Mar 2024 12:44:36 +0200

> Date: Sat, 16 Mar 2024 23:29:52 -0500
> Cc: 69666 <at> debbugs.gnu.org
> From: Adam Porter <adam <at> alphapapa.net>
> 
> Thanks, please see the attached patch.

Thanks, installed, and closing the bug.

> For future reference, is there a way to know whether the heading line is
> too long for the ChangeLog entry, other than manually counting?

I suggest to arrange for fill-column to be set in the buffers where
you edit the log messages, then M-q or auto-fill-mode will do this for
you.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.