From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: giecrilj@stegny.2a.pl, 10106@debbugs.gnu.org
Subject: bug#10106: 23.2; how to pass command arguments to gud-go
Date: Wed, 11 May 2022 14:27:10 +0200 [thread overview]
Message-ID: <87y1z89rvl.fsf@gnus.org> (raw)
In-Reply-To: <83zgjoqnth.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 11 May 2022 15:02:50 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Yes, I think this is correct.
Thanks; pushed to the trunk now.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-05-11 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 11:08 bug#10106: 23.2; how to pass command arguments to gud-go Krzysztof =17belechowski
2022-05-10 4:24 ` Lars Ingebrigtsen
2022-05-10 11:56 ` Eli Zaretskii
2022-05-11 11:31 ` Lars Ingebrigtsen
2022-05-11 12:02 ` Eli Zaretskii
2022-05-11 12:27 ` Lars Ingebrigtsen [this message]
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=87y1z89rvl.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=10106@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=giecrilj@stegny.2a.pl \
/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).