From: Joel Brobecker <brobecker@adacore.com>
To: Daniel Gutson <dgutson@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: write after approval privs request
Date: Thu, 12 Nov 2009 01:00:00 -0000 [thread overview]
Message-ID: <20091111020013.GJ11716@adacore.com> (raw)
In-Reply-To: <4AFA0CF3.1080208@codesourcery.com>
> since I'm submitting a number of patches, could I have write after
> approval privs, so I don't bother other people asking to commit those
> for me?
Of course. Do you have an account on sourceware.org? If not, please
fill in the following form. You can list me as your sponsor. This
should get you all setup for write access very quickly. Once you have
write access, checkout the sources, and commit a change to gdb/MAINTAINERS
that adds you to the Write After Approval list. This is a good way to
verify that your write access works. Please be sure to send the
corresponding patch, with ChangeLog, to gdb-patches.
Welcome to the group,
--
Joel
next prev parent reply other threads:[~2009-11-11 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 0:22 Daniel Gutson
2009-11-12 1:00 ` Joel Brobecker [this message]
2009-11-12 1:06 ` Joel Brobecker
2013-02-20 3:10 Jiong Wang
2013-02-20 3:25 ` Joel Brobecker
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=20091111020013.GJ11716@adacore.com \
--to=brobecker@adacore.com \
--cc=dgutson@codesourcery.com \
--cc=gdb@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