From: Kevin Buettner via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Document how GDB searches for files when using -s, -e, and -se options
Date: Tue, 21 Jun 2022 09:50:10 -0700 [thread overview]
Message-ID: <20220621095010.23e59e5f@f35-zws-1> (raw)
In-Reply-To: <83sfnyj9oo.fsf@gnu.org>
On Tue, 21 Jun 2022 18:52:23 +0300
Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Tue, 21 Jun 2022 08:40:43 -0700
> > From: Kevin Buettner <kevinb@redhat.com>
> > Cc: Eli Zaretskii <eliz@gnu.org>
> >
> > Ping.
>
> This is OK, and sorry for the delay.
I've pushed it.
prev parent reply other threads:[~2022-06-21 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 17:04 Kevin Buettner via Gdb-patches
2022-06-21 15:40 ` Kevin Buettner via Gdb-patches
2022-06-21 15:52 ` Eli Zaretskii via Gdb-patches
2022-06-21 16:50 ` Kevin Buettner via Gdb-patches [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=20220621095010.23e59e5f@f35-zws-1 \
--to=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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