From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: rolling 5.3.92 tomorrow
Date: Thu, 11 Sep 2003 17:46:00 -0000 [thread overview]
Message-ID: <200309111746.h8BHk11V003424@duracef.shout.net> (raw)
drow> The only other issue I know of is that Mark's per-objfile-data patch,
drow> and my fix for the assertion failures in Java, aren't on the branch
drow> yet. Should we move those patches over?
I would love to have the Java assertion patch on the branch.
It's a very localized patch -- it just changes the order of
two tests, really. It's easy to verify that it can't break
anything. And on the upside, it fixes a crash bug.
Michael C
next reply other threads:[~2003-09-11 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 17:46 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-11 20:12 Michael Elizabeth Chastain
2003-09-11 17:41 Michael Elizabeth Chastain
2003-09-11 14:22 Andrew Cagney
2003-09-11 14:37 ` Daniel Jacobowitz
2003-09-11 17:53 ` Elena Zannoni
2003-09-14 18:36 ` Daniel Jacobowitz
2003-09-11 19:47 ` Andrew Cagney
2003-09-13 0:54 ` Jim Blandy
2003-09-14 23:50 ` Andrew Cagney
2003-09-15 0:01 ` Daniel Jacobowitz
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=200309111746.h8BHk11V003424@duracef.shout.net \
--to=mec@shout.net \
--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