From: Andrew Cagney <cagney@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: write after approval
Date: Fri, 19 Jan 2007 16:34:00 -0000 [thread overview]
Message-ID: <45B0F2F5.4000301@redhat.com> (raw)
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.
Andrew
next reply other threads:[~2007-01-19 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 16:34 Andrew Cagney [this message]
2007-01-20 4:34 ` Daniel Jacobowitz
-- 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=45B0F2F5.4000301@redhat.com \
--to=cagney@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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