From: Eli Zaretskii <eliz@gnu.org>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] inferior without argument prints detail of current inferior
Date: Sun, 10 Jan 2021 18:41:04 +0200 [thread overview]
Message-ID: <83a6tghhi7.fsf@gnu.org> (raw)
In-Reply-To: <20210109212416.10681-1-lsix@lancelotsix.com> (message from Lancelot SIX via Gdb-patches on Sat, 9 Jan 2021 21:24:16 +0000)
> Date: Sat, 9 Jan 2021 21:24:16 +0000
> From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Lancelot SIX <lsix@lancelotsix.com>
>
> Changes from V1:
> * Add test.
>
> Change from V2:
> * Fix gdb/doc/ChangeLog entry.
> * My copyright assignment has been signed.
>
> gdb/doc/ChangeLog:
>
> * gdb.texinfo (Inferiors Connections and Programs): Document the
> inferior command when used without argument.
>
> gdb/ChangeLog:
>
> * inferior.c (inferior_command): When no argument is given to the
> inferior command, display info about the currently selected
> inferior.
>
> gdb/testsuite/ChangeLog:
>
> * gdb.base/inferior-noarg.c: New test.
> * gdb.base/inferior-noarg.exp: New test.
OK for the documentation part, but does this warrant a NEWS entry as
well?
Thanks.
next prev parent reply other threads:[~2021-01-10 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 22:04 [PATCH v2] " Lancelot SIX
2020-12-18 22:24 ` Simon Marchi
2021-01-09 21:24 ` [PATCH v3] " Lancelot SIX
2021-01-10 16:00 ` Simon Marchi
2021-01-10 17:37 ` Lancelot SIX
2021-01-11 1:06 ` Simon Marchi
2021-01-10 16:41 ` Eli Zaretskii [this message]
2021-01-10 17:38 ` Lancelot SIX
2021-01-10 17:58 ` [PATCH v4] " Lancelot SIX
2021-01-11 1:14 ` Simon Marchi
2021-01-11 14:57 ` Eli Zaretskii
2021-02-02 22:44 ` Lancelot SIX
2021-02-02 22:59 ` Simon Marchi
2021-02-02 23:04 ` Lancelot SIX
2021-02-02 23:37 ` Simon Marchi
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=83a6tghhi7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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.
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).