From: Carl Love <cel@us.ibm.com>
To: Simon Marchi <simark@simark.ca>
Cc: Carl Love <cel@us.ibm.com>,
dje@google.com, gdb-patches@sourceware.org,
Rogerio Alves <rogealve@br.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: Re: [PATCH] Fix for gdb.base/solib-search.exp test.
Date: Thu, 21 Apr 2022 12:16:33 -0700 [thread overview]
Message-ID: <fa19a4bfc5bc01b615999430eb3839d53eff146a.camel@us.ibm.com> (raw)
In-Reply-To: <bd16e7df-a650-9fbd-7188-3889ce0445fd@simark.ca>
On Thu, 2022-04-21 at 15:04 -0400, Simon Marchi wrote:
>
<snip>
>
> Cool, can you integrate the info above in your commit message? That
> makes the problem clearer for somebody not in your seat. The patch
> is
> ok with that changed, thanks.
Yup, will do. Thanks.
Carl
next prev parent reply other threads:[~2022-04-21 19:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 21:49 Carl Love
2022-03-28 15:21 ` [PING] " Carl Love
2022-04-07 15:13 ` [PING 2] " Carl Love
2022-04-21 1:49 ` [PING 3] " Carl Love
2022-04-21 13:39 ` Simon Marchi
2022-04-21 18:21 ` Carl Love
2022-04-21 19:04 ` Simon Marchi
2022-04-21 19:16 ` Carl Love [this message]
2022-04-21 15:05 ` will schmidt
2022-05-02 14:16 ` Ulrich Weigand
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=fa19a4bfc5bc01b615999430eb3839d53eff146a.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=rogealve@br.ibm.com \
--cc=simark@simark.ca \
--cc=will_schmidt@vnet.ibm.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).