public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: gdb-patches@sourceware.org
Cc: Louis-He <1726110778@qq.com>,
	Dominique Quatravaux <dominique.quatravaux@epfl.ch>,
	Sam Warner <samuuel.r.warner@me.com>
Subject: Re: [[RFC][PATCH][PR gdb/24069]] gdb/testsuite/README: update default value of INTERNAL_GDBFLAGS
Date: Sat, 19 Feb 2022 16:37:27 -0500	[thread overview]
Message-ID: <a395af91-42e7-94e4-11dc-365b4dfc9be6@gmail.com> (raw)
In-Reply-To: <20220219212442.18136-1-levraiphilippeblain@gmail.com>

Hello, 

Le 2022-02-19 à 16:24, Philippe Blain via Gdb-patches a écrit :
> The INTERNAL_GDBFLAGS runtest variable was updated in 55c3ad88013

I'm sorry to have disturbed you all with these erronous CCs. I'm a little new
to the whole git send-email dance and went a little fast. 

You can disregard this patch, I'll send a new mail with the right CCs and
a better title.

Philippe.

      reply	other threads:[~2022-02-19 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19 21:24 Philippe Blain
2022-02-19 21:37 ` Philippe Blain [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=a395af91-42e7-94e4-11dc-365b4dfc9be6@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=1726110778@qq.com \
    --cc=dominique.quatravaux@epfl.ch \
    --cc=gdb-patches@sourceware.org \
    --cc=samuuel.r.warner@me.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).