unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 60312@debbugs.gnu.org, bugs@gnu.support, raman@google.com
Subject: bug#60312: 30.0.50; Feature Request: Customize yes-or-n-p prompt from elisp:
Date: Tue, 03 Jan 2023 17:32:09 +0200	[thread overview]
Message-ID: <83y1qjzlae.fsf@gnu.org> (raw)
In-Reply-To: <87h6x7k5y8.fsf@gmail.com> (message from Robert Pluim on Tue, 03 Jan 2023 16:12:31 +0100)

> 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.





  reply	other threads:[~2023-01-03 15:32 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 [this message]
2023-01-23  8:23           ` Robert Pluim
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

  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=83y1qjzlae.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60312@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    --cc=raman@google.com \
    --cc=rpluim@gmail.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).