Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
	 gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: Prepare for DejaGnu 1.6.2
Date: Thu, 07 Mar 2019 21:55:00 -0000	[thread overview]
Message-ID: <8736nyic3c.fsf@tromey.com> (raw)
In-Reply-To: <87r2bielg0.fsf@redhat.com> (Sergio Durigan Junior's message of	"Thu, 07 Mar 2019 10:46:55 -0500")

>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:

Sergio> FWIW, I've always found these "load_lib gdb.exp" to be remnants of an
Sergio> old past, and not needed anymore (or even buggy).  Thanks for the
Sergio> investigation; IMO, the patch is fine could almost be considered an
Sergio> "obvious" cleanup.  I'm not a global maintainer, though.

Thanks for looking at this.
This is ok.

Tom


  reply	other threads:[~2019-03-07 21:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 14:04 Andrew Burgess
2019-03-07 15:46 ` Sergio Durigan Junior
2019-03-07 21:55   ` Tom Tromey [this message]
2019-03-26 21:14 ` Pedro Franco de Carvalho
2019-03-26 22:44   ` Joel Brobecker

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=8736nyic3c.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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