From: Gary Benson <gbenson@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb@sourceware.org
Subject: Re: Problematic .gdb_index warning regexps in testsuite
Date: Fri, 20 Apr 2012 10:30:00 -0000 [thread overview]
Message-ID: <20120420102948.GA4264@redhat.com> (raw)
In-Reply-To: <20120420101159.GA16774@host2.jankratochvil.net>
On Thu, 19 Apr 2012 17:11:45 +0200, Doug Evans wrote:
> I think we don't want to go down this path. This will just
> proliferate, and make tests unnecessarily bulkier (harder to
> maintain) than they should be.
It wasn't very nice, I agree.
Jan Kratochvil wrote:
> Sure there could be also made some lib/gdb.exp:
> set warning obsolete gdb-index off
> which could also be unified with renaming of current uncommited
> set auto-load local-gdbinit-warning off
> ->
> set warning obsolete local-gdbinit off
> or something like that.
I can make a patch to add a "set warning obsolete gdb-index off" if
you like. Just let me know...
Cheers,
Gary
--
http://gbenson.net/
prev parent reply other threads:[~2012-04-20 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 15:12 Doug Evans
2012-04-20 10:12 ` Jan Kratochvil
2012-04-20 10:18 ` Jan Kratochvil
2012-04-20 10:30 ` Gary Benson [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=20120420102948.GA4264@redhat.com \
--to=gbenson@redhat.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).