From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: raman@google.com, bugs@gnu.support, 60312@debbugs.gnu.org
Subject: bug#60312: 30.0.50; Feature Request: Customize yes-or-n-p prompt from elisp:
Date: Mon, 23 Jan 2023 09:23:21 +0100 [thread overview]
Message-ID: <87zga91wxy.fsf@gmail.com> (raw)
In-Reply-To: <83y1qjzlae.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 03 Jan 2023 17:32:09 +0200")
tags 60312 fixed
close 60312 30.1
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: bugs@gnu.support, 60312@debbugs.gnu.org,
>> Eli Zaretskii <eliz@gnu.org>
>> Date: Tue, 03 Jan 2023 16:12:31 +0100
>>
>> >>>>> On Tue, 3 Jan 2023 07:06:24 -0800, "T.V Raman" <raman@google.com> said:
>>
>> TV> this SGTM.
>>
>> Thanks. Iʼll work on getting it out to master this week (assuming Eli
>> has no objections)
>
> None.
>
> Thanks.
Closing.
Committed as 26ef5c09e0
Thanks
Robert
--
next prev parent reply other threads:[~2023-01-23 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 15:22 bug#60312: 30.0.50; Feature Request: Customize yes-or-n-p prompt from elisp: T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.60312.B.167198177811134.ack@debbugs.gnu.org>
2022-12-25 15:53 ` bug#60312: Acknowledgement (30.0.50; Feature Request: Customize yes-or-n-p prompt from elisp:) T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-25 17:19 ` bug#60312: 30.0.50; Feature Request: Customize yes-or-n-p prompt from elisp: Jean Louis
2023-01-03 14:52 ` Robert Pluim
2023-01-03 15:06 ` T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-03 15:12 ` Robert Pluim
2023-01-03 15:32 ` Eli Zaretskii
2023-01-23 8:23 ` Robert Pluim [this message]
2023-09-10 17:35 ` Stefan Kangas
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=87zga91wxy.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=60312@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=eliz@gnu.org \
--cc=raman@google.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.