From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: write after approval
Date: Sat, 20 Jan 2007 04:34:00 -0000 [thread overview]
Message-ID: <20070120043406.GA22013@nevyn.them.org> (raw)
In-Reply-To: <45B0F2F5.4000301@redhat.com>
On Fri, Jan 19, 2007 at 11:33:57AM -0500, Andrew Cagney wrote:
> Jan,
>
> Assuming that CGF makes the necessary account changes. You should feel
> free to add yourself to the write-after-approval list; don't forget the
> ChangeLog entry.
>
> I've been watching your multiple submitions for 6 months now, and with
> an assignment covered by Red Hat, you certainly qualify.
Thank you for taking care of this.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-20 4:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 16:34 Andrew Cagney
2007-01-20 4:34 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-15 16:05 Andrew Cagney
2001-04-25 10:26 Write " Don Howard
2001-04-26 20:46 ` Andrew Cagney
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=20070120043406.GA22013@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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