From: Bob Rossi <bob@brasko.net>
To: GDB <gdb@sources.redhat.com>
Subject: Head Maintainer Action
Date: Sat, 05 Mar 2005 22:15:00 -0000 [thread overview]
Message-ID: <20050305221553.GB4481@white> (raw)
Hi,
Andrew, could you please put on your head maintainer hat and ask
"Andrew, the MI maintainer" if he could possibly work with me a little
faster, so that I could make a significant contribution to GDB/MI?
Also, if "Andrew the MI maintainer" is busy with other stuff, could you
find out who would be able to work with me? I have a lot of ideas, and
would like to be able to contribute them to GDB/MI, so that other front
end developers will not be wasting there time.
I asked "Andrew the MI maintainer" if he could review my patch, so that
I could get other work done, but there was no reply ...
http://sources.redhat.com/ml/gdb-patches/2005-03/msg00013.html
Thanks,
Bob Rossi
reply other threads:[~2005-03-05 22:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050305221553.GB4481@white \
--to=bob@brasko.net \
--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