From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@mvista.com, mec.gnu@mindspring.com
Cc: carlton@kealia.com, gdb@sources.redhat.com
Subject: Re: gcc 3.4 regression in gdb.cp/namespace.exp
Date: Tue, 16 Mar 2004 16:33:00 -0000 [thread overview]
Message-ID: <20040316163351.354B74B104@berman.michael-chastain.com> (raw)
> Have you run it since I committed the process_structure_scope patch on
> Saturday? I won't have time to really parse David's explanation for a
> couple of days but it sounds like I broke this.
No, my last spin was for Monday, 2004-03-08.
I have another spin in progress for Sunday, 2004-03-14 15:04:08 UTC, but
you committed that patch on 2004-03-14 21:08:24 UTC so it's not in my
current spin. Rats.
Michael C
next reply other threads:[~2004-03-16 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 16:33 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-16 2:39 Michael Elizabeth Chastain
2004-03-16 16:00 ` Daniel Jacobowitz
2004-03-16 16:37 ` David Carlton
2004-03-16 0:23 David Carlton
2004-03-16 18:25 ` David Carlton
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=20040316163351.354B74B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=carlton@kealia.com \
--cc=drow@mvista.com \
--cc=gdb@sources.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