From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, christina.schimpe@intel.com
Subject: Re: [PATCH 1/1] doc: fix informations typo in gdb.texinfo
Date: Tue, 28 Mar 2023 20:01:56 +0300 [thread overview]
Message-ID: <83zg7w7qt7.fsf@gnu.org> (raw)
In-Reply-To: <87h6u4dh1t.fsf@tromey.com> (message from Tom Tromey on Tue, 28 Mar 2023 09:36:14 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Christina Schimpe <christina.schimpe@intel.com>
> Date: Tue, 28 Mar 2023 09:36:14 -0600
>
> >>>>> Christina Schimpe via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> > From: Nils-Christian Kempke <nils-christian.kempke@intel.com>
> > Co-Authored-By: Christina Schimpe <christina.schimpe@intel.com>
> > ---
> > gdb/doc/gdb.texinfo | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
>
> FWIW I think this is obviously correct & so you should check it in.
Indeed.
next prev parent reply other threads:[~2023-03-28 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 8:55 [PATCH 0/1] Fix typos " Christina Schimpe
2023-03-28 8:55 ` [PATCH 1/1] doc: fix informations typo " Christina Schimpe
2023-03-28 15:36 ` Tom Tromey
2023-03-28 17:01 ` Eli Zaretskii [this message]
2023-03-29 12:23 ` Schimpe, Christina
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=83zg7w7qt7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).