From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, Ian Lance Taylor <ian@airs.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Correct memset calls in ser-{pipe,tcp,unix}.c
Date: Tue, 13 May 2003 19:49:00 -0000 [thread overview]
Message-ID: <3EC14C36.70201@redhat.com> (raw)
In-Reply-To: <20030513193515.GA13984@nevyn.them.org>
Ian,
Can you also add your self to GDB's write after approval list in the
gdb/MAINTAINERS (don't forget to post the ChangeLog/change) and, since
you're able to, the gdb group on sware.
enjoy,
Andrew
> On Tue, May 13, 2003 at 11:29:16AM -0700, Ian Lance Taylor wrote:
>
>> Any word on this patch? Is this OK to check in?
>>
>> http://sources.redhat.com/ml/gdb-patches/2003-05/msg00077.html
>
>
> Yes, please.
>
> -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-13 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 18:29 Ian Lance Taylor
2003-05-13 19:35 ` Daniel Jacobowitz
2003-05-13 19:49 ` Andrew Cagney [this message]
2003-05-13 19:53 ` PATCH: Add myself to MAINTAINERS write after approval list Ian Lance Taylor
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=3EC14C36.70201@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=ian@airs.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