From: Bob Rossi <bob@brasko.net>
To: Kip Macy <kmacy@fsmware.com>
Cc: gdb@sources.redhat.com
Subject: Re: [MI] -file-list-exec-source-files
Date: Mon, 16 Feb 2004 03:19:00 -0000 [thread overview]
Message-ID: <20040216031921.GA3379@white> (raw)
In-Reply-To: <20040215173938.R69105@demos.bsdclusters.com>
On Sun, Feb 15, 2004 at 05:42:27PM -0800, Kip Macy wrote:
> My limited experience indicates that it can take up to 7 days to get
> feedback on an idea on this list. At this point the best thing to do
> is sit tight :-).
I wonder if there is something that could be done to improve this ...
Waiting 7 days for a response is acceptable if need be, but from a
"scheduling" point of view, it seems rather lacking.
Is there anything I could do to help improve the response time of the
GDB developers? In general, I am pretty interested in implementing some
of the missing MI commands. However, I don't really have the time to
wait 7 days for every stumbling block that I run up against.
Should I Email the MI Maintainers directly? Or would this be bad taste?
Bob Rossi
next prev parent reply other threads:[~2004-02-16 3:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 1:29 Bob Rossi
2004-02-16 1:26 ` Bob Rossi
2004-02-16 1:42 ` Kip Macy
2004-02-16 3:19 ` Bob Rossi [this message]
2004-02-16 3:30 ` Daniel Jacobowitz
2004-02-16 3:45 ` Bob Rossi
2004-02-16 3:49 ` Daniel Jacobowitz
2004-02-16 15:33 ` Bob Rossi
2004-02-16 15:46 ` Daniel Jacobowitz
2004-02-16 16:08 ` Bob Rossi
2004-02-17 18:22 ` Andrew Cagney
2004-02-17 19:10 ` Bob Rossi
2004-02-17 19:12 ` Daniel Jacobowitz
2004-02-17 19:30 ` Bob Rossi
2004-02-17 19:33 ` Daniel Jacobowitz
2004-02-23 13:13 ` Bob Rossi
2004-02-23 13:55 ` Daniel Jacobowitz
2004-02-24 4:26 ` Bob Rossi
2004-02-27 6:23 ` Bob Rossi
2004-02-27 15:00 ` Daniel Jacobowitz
2004-02-17 19:47 ` Andrew Cagney
2004-02-17 20:02 ` Bob Rossi
2004-02-17 20:27 ` Andrew Cagney
2004-02-17 21:08 ` Bob Rossi
2004-02-17 21:37 ` Daniel Jacobowitz
2004-02-17 21:58 ` Bob Rossi
2004-02-18 14:24 ` Alain Magloire
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=20040216031921.GA3379@white \
--to=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=kmacy@fsmware.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