From: Michael Chastain <mec.gnu@mindspring.com>
To: monika@acmet.com, gdb@sources.redhat.com
Subject: Re: debugger 6.2.1 misfeatures
Date: Sat, 11 Sep 2004 15:52:00 -0000 [thread overview]
Message-ID: <41431F49.nailCH317KU2M@mindspring.com> (raw)
In-Reply-To: <004501c497e5$a53cd9b0$5100a8c0@monika>
"Monika Chaddha" <monika@acmet.com> wrote:
> Is it necessary to send test cases with the bug?
Depends on the bug. It's necessary to send enough info for someone
else to reproduce the bug.
> I had sent the following bug with patch some days ago but didn't get any
> response regarding this. I don't have any test case till now to prove
> this bug as it can be test only for remote target during tracing. What
> should I do? Pls help.
First check the file sim/MAINTAINERS and make sure you're sending
to the specific maintainer as well as gdb-patches@.
Post. Wait a week, then send it again with a note indicating that it's
a repost, with the dates of the previous post. Wait another week, do it
again (with all the previous dates). Wait another week, do it again.
Wait another week, do it again. Wait another week, do it again.
After a month of this, start a separate thread asking for an additional
maintainer for the area that you're patching.
The longest I've had to wait this year has been 125 days.
Michael Chastain
honor fdny -- give blood
next prev parent reply other threads:[~2004-09-11 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 0:05 Edward Peschko
2004-09-11 1:46 ` Michael Chastain
2004-09-11 9:59 ` Monika Chaddha
2004-09-11 15:52 ` Michael Chastain [this message]
2004-09-13 7:01 ` Monika Chaddha
2004-09-11 16:26 ` Joel Brobecker
2004-09-15 6:37 ` Joel Brobecker
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=41431F49.nailCH317KU2M@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb@sources.redhat.com \
--cc=monika@acmet.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