From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Denis PILAT <denis.pilat@st.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Target stderr not displayed thru MI
Date: Tue, 06 Dec 2005 10:49:00 -0000 [thread overview]
Message-ID: <20051205144042.GA4984@nevyn.them.org> (raw)
In-Reply-To: <17300.5919.453393.497373@kahikatea.snap.net.nz>
On Mon, Dec 05, 2005 at 11:31:59PM +1300, Nick Roberts wrote:
> > Nick,
> >
> > Can I consider that my original patch
> > (http://sources.redhat.com/ml/gdb-patches/2005-11/msg00497.html) is
> > accepted ?
> >
> > Denis
>
> I don't have the authority to approve it. I only have "Write After Approval"
> and an interest in MI. According to the rules in the MAINTAINERS file, since
> there is no longer a maintainer for MI, the responsibility falls to a global
> maintainer such as Daniel Jacobowitz or Jim Blandy.
The patch is OK; Jim already approved it conditional on feedback, Nick
was the only one to suggest a change, and we've agreed that the change
is unnecessary for the moment.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-12-05 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 14:15 Nick Roberts
2005-11-30 18:57 ` [PATCH] " Denis PILAT
2005-11-30 19:03 ` Bob Rossi
2005-11-30 19:55 ` Daniel Jacobowitz
[not found] ` <17294.2894.345752.773239@kahikatea.snap.net.nz>
2005-12-01 13:57 ` Denis PILAT
2005-12-01 14:06 ` Bob Rossi
2005-12-01 14:32 ` Daniel Jacobowitz
2005-12-01 16:20 ` Denis PILAT
2005-12-01 22:49 ` Nick Roberts
2005-12-02 1:26 ` Jim Blandy
2005-12-05 20:50 ` Denis PILAT
2005-12-06 6:09 ` Nick Roberts
2005-12-06 10:49 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-30 2:47 Denis PILAT
2005-11-30 13:51 ` Jim Blandy
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=20051205144042.GA4984@nevyn.them.org \
--to=drow@false.org \
--cc=denis.pilat@st.com \
--cc=gdb-patches@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