From: Chris Moller <cmoller@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Daniel Jacobowitz <dan@codesourcery.com>,
Roland McGrath <roland@redhat.com>,
Project Archer <archer@sourceware.org>
Subject: Re: PR 11067
Date: Thu, 04 Feb 2010 17:30:00 -0000 [thread overview]
Message-ID: <4B6B041A.4030307@redhat.com> (raw)
In-Reply-To: <m3eil1okew.fsf@fleche.redhat.com>
Just FYI, this patch breaks a handful of existing tests:
gdb.base/setvar.exp
gdb.cp/classes.exp
gdb.cp/m-data.exp
gdb.cp/m-static.exp
cp/namespace.exp
gdb.mi/mi-var-display.exp
gdb.python/py-value.exp
None of them are hard to fix in the expects--I just wanted The World to
realise that there are going to be noticeable consequences to this
fairly minor nicety. It'll take me a bit to fix the t/cs--if The Powers
That Be would rather this patch not proceed, I'd appreciate it if you'd
let me know sooner rather than later and spare me all the fix-up work.
next prev parent reply other threads:[~2010-02-04 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 22:12 patch for pr9067 Chris Moller
2010-02-02 23:28 ` Tom Tromey
2010-02-03 2:25 ` Chris Moller
2010-02-03 20:04 ` Tom Tromey
[not found] ` <m3bpg7yznc.fsf@fleche.redhat.com>
[not found] ` <4B68DC25.1090808@redhat.com>
[not found] ` <m3fx5irwx6.fsf@fleche.redhat.com>
2010-02-03 21:52 ` PR 11067 Chris Moller
2010-02-03 22:43 ` Roland McGrath
2010-02-03 22:48 ` Tom Tromey
2010-02-03 23:14 ` Daniel Jacobowitz
2010-02-03 23:25 ` Roland McGrath
2010-02-03 23:30 ` Daniel Jacobowitz
2010-02-03 23:34 ` Chris Moller
2010-02-04 1:32 ` Tom Tromey
2010-02-04 17:30 ` Chris Moller [this message]
2010-02-04 23:53 ` Tom Tromey
2010-02-05 0:29 ` Chris Moller
2010-02-05 20:19 ` Roland McGrath
2010-02-05 22:52 ` Chris Moller
2010-02-03 23:21 ` Chris Moller
2010-02-03 22:47 ` Tom Tromey
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=4B6B041A.4030307@redhat.com \
--to=cmoller@redhat.com \
--cc=archer@sourceware.org \
--cc=dan@codesourcery.com \
--cc=roland@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).