From: Andrew Cagney <ac131313@redhat.com>
To: shrinivasa@kpitcummins.com, gdb-patches@sources.redhat.com
Subject: write after approval
Date: Fri, 15 Aug 2003 16:05:00 -0000 [thread overview]
Message-ID: <3F3CFE7B.8070009@redhat.com> (raw)
Shrinivas, your account should be available. Can you please check it
out by adding your self to the write-after-approval list.
enjoy,
Andrew
PS: It's sorted alpabetically. Don't forget to make a ChangeLog entry
and post a patch.
next reply other threads:[~2003-08-15 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 16:05 Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-19 16:34 Andrew Cagney
2007-01-20 4:34 ` Daniel Jacobowitz
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=3F3CFE7B.8070009@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=shrinivasa@kpitcummins.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