From: Guinevere Larsen <guinevere@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdb: add tutorial command
Date: Thu, 5 Mar 2026 10:35:54 -0300 [thread overview]
Message-ID: <9c913738-ec7d-4073-9434-f696d12e536c@redhat.com> (raw)
In-Reply-To: <861phywgh6.fsf@gnu.org>
On 3/5/26 10:31 AM, Eli Zaretskii wrote:
>> Date: Thu, 5 Mar 2026 09:23:03 -0300
>> Cc: Eli Zaretskii <eliz@gnu.org>
>> From: Guinevere Larsen <guinevere@redhat.com>
>>
>> Ping :)
> I already approved the documentation parts, didn't I?
>
Yes sorry. I used the "reply all" button, which emailed you directly
because you were in the original CC list. Sorry for the noise, nothing
needed from you
--
Cheers,
Guinevere Larsen
It/she
prev parent reply other threads:[~2026-03-05 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 19:33 Guinevere Larsen
2026-01-28 19:44 ` Eli Zaretskii
2026-03-05 12:23 ` Guinevere Larsen
2026-03-05 13:31 ` Eli Zaretskii
2026-03-05 13:35 ` Guinevere Larsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c913738-ec7d-4073-9434-f696d12e536c@redhat.com \
--to=guinevere@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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