From: "Eli Zaretskii" <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: MI Maintanance
Date: Sun, 17 Apr 2005 03:33:00 -0000 [thread overview]
Message-ID: <01c542fd$Blat.v2.4$bef65160@zahav.net.il> (raw)
In-Reply-To: <16993.34163.414589.888781@farnswood.snap.net.nz> (message from Nick Roberts on Sun, 17 Apr 2005 09:36:51 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sun, 17 Apr 2005 09:36:51 +1200
>
> Focussing on the practical, is it possible to find new maintainers for this
> aspect of GDB?
As Daniel wrote, they have been found. I suggest that people who sent
MI patches in the past start pinging with URLs to the respective
messages. (If possible, be gentle with us: don't post too many pings
at once ;-)
prev parent reply other threads:[~2005-04-17 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 21:37 Nick Roberts
2005-04-17 2:09 ` Daniel Jacobowitz
2005-04-17 3:33 ` Eli Zaretskii [this message]
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='01c542fd$Blat.v2.4$bef65160@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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