From: Michael Elizabeth Chastain <mec@shout.net>
To: ezannoni@redhat.com, jimb@redhat.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] import drow dbxread.c fix to branch
Date: Fri, 05 Apr 2002 13:34:00 -0000 [thread overview]
Message-ID: <200204052134.g35LYiF18389@duracef.shout.net> (raw)
Jim Blandy writes:
> Perhaps this is bad attitude on my part, but I think we should go
> ahead with the changes (which we know are helpful), and wait until the
> older problem surfaces.
Sounds good to me.
DanielJ's patches have all been in areas unrelated to FredF's original
patch. What's more, they are fixing more than FredF's patch broke.
So I'm happy with the path we are on. I just want to nail all the
regressions in the 5.2 branch before it ships.
Michael C
next reply other threads:[~2002-04-05 21:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 13:34 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-04 18:17 Michael Elizabeth Chastain
2002-04-04 18:36 ` Daniel Jacobowitz
2002-04-04 19:35 ` Elena Zannoni
2002-04-05 13:10 ` Jim Blandy
2002-04-05 13:16 ` Daniel Jacobowitz
2002-04-04 8:37 Michael Elizabeth Chastain
2002-04-03 21:36 Michael Elizabeth Chastain
2002-04-03 22:01 ` Daniel Jacobowitz
2002-04-04 10:58 ` Andrew Cagney
2002-04-04 11:33 ` Elena Zannoni
2002-04-04 11:40 ` Daniel Jacobowitz
2002-04-04 12:15 ` Elena Zannoni
2002-04-04 12:24 ` Daniel Jacobowitz
2002-04-04 12:18 ` Andrew Cagney
2002-04-04 12:20 ` Daniel Berlin
2002-04-04 12:30 ` Andrew Cagney
2002-04-03 20:48 Michael Elizabeth Chastain
2002-04-03 21:09 ` Daniel Jacobowitz
2002-04-01 21:36 Michael Elizabeth Chastain
2002-04-01 21:43 ` Eli Zaretskii
2002-04-03 19:43 ` Andrew Cagney
2002-04-01 11:22 Michael Elizabeth Chastain
2002-04-01 20:49 ` Eli Zaretskii
2002-04-01 8:56 Michael Elizabeth Chastain
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=200204052134.g35LYiF18389@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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