From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix gdb.base/macscp.exp when using custom inputrc
Date: Mon, 13 Jul 2009 19:35:00 -0000 [thread overview]
Message-ID: <20090713192457.GA2061@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3ws6cpix2.fsf@fleche.redhat.com>
On Mon, 13 Jul 2009 19:55:05 +0200, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> gdb/testsuite/
> Jan> 2009-07-12 Jan Kratochvil <jan.kratochvil@redhat.com>
> Jan> Fix gdb.base/macscp.exp when using custom inputrc.
> Jan> * gdb.base/completion.exp: Remove env(INPUTRC) set and restore.
> Jan> * gdb.base/readline.exp: Remove env(INPUTRC) set and restore. Remove
> Jan> env(TERM) set.
> Jan> * gdb.cp/cpcompletion.exp: Remove env(INPUTRC) set.
> Jan> * lib/gdb.exp (default_gdb_start): Add env(INPUTRC) and env(TERM) set.
>
> Thanks, this patch is ok.
Checked-in:
http://sourceware.org/ml/gdb-cvs/2009-07/msg00101.html
Thanks,
Jan
prev parent reply other threads:[~2009-07-13 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 14:26 Jan Kratochvil
2009-07-13 18:16 ` Tom Tromey
2009-07-13 19:35 ` Jan Kratochvil [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=20090713192457.GA2061@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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