From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: "Nathan J. Williams" <nathanw@wasabisystems.com>,
gdb-patches@sources.redhat.com
Subject: Re: [patch] gdbserver: Detect and return errors reading memory
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040305041936.GJ5320@nevyn.them.org> (raw)
In-Reply-To: <4047FE0C.8030805@gnu.org>
On Thu, Mar 04, 2004 at 11:11:56PM -0500, Andrew Cagney wrote:
> >Committed to HEAD and GDB 6.1. You now qualify for
> >write-after-approval access; if you want to apply, wander over to the
> >sources.redhat.com site and fill out the form. There's a link to it
> >about halfway down the front page, under Occasional Questions.
>
> I'll assume that you're recommending Nathan for write-after-approval?
Yes, I think that was obvious from my message.
> I've taken care of it (remember, maintenance issues are normally handled
> off list).
What needed to be taken care of, for my own education?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: "Nathan J. Williams" <nathanw@wasabisystems.com>,
gdb-patches@sources.redhat.com
Subject: Re: [patch] gdbserver: Detect and return errors reading memory
Date: Fri, 05 Mar 2004 04:19:00 -0000 [thread overview]
Message-ID: <20040305041936.GJ5320@nevyn.them.org> (raw)
Message-ID: <20040305041900.wXRAloq9cy_qfBiv_pWhObjWvO2ncJSbNQH_cFdQRaE@z> (raw)
In-Reply-To: <4047FE0C.8030805@gnu.org>
On Thu, Mar 04, 2004 at 11:11:56PM -0500, Andrew Cagney wrote:
> >Committed to HEAD and GDB 6.1. You now qualify for
> >write-after-approval access; if you want to apply, wander over to the
> >sources.redhat.com site and fill out the form. There's a link to it
> >about halfway down the front page, under Occasional Questions.
>
> I'll assume that you're recommending Nathan for write-after-approval?
Yes, I think that was obvious from my message.
> I've taken care of it (remember, maintenance issues are normally handled
> off list).
What needed to be taken care of, for my own education?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-05 4:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 20:55 Nathan J. Williams
2004-03-05 2:59 ` Daniel Jacobowitz
2004-03-05 3:37 ` Nathan J. Williams
2004-03-19 0:09 ` Nathan J. Williams
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-05 3:48 ` Daniel Jacobowitz
2004-03-05 4:12 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz [this message]
2004-03-05 4:19 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Nathan J. Williams
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=20040305041936.GJ5320@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nathanw@wasabisystems.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