public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Oleg Endo <oleg.endo@t-online.de>
To: overseers@sourceware.org
Cc: Kaz Kojima <kkojima@rr.iij4u.or.jp>, Nicholas Clifton <nickc@redhat.com>
Subject: Re: binutils write access
Date: Tue, 24 Feb 2015 10:14:00 -0000	[thread overview]
Message-ID: <1424772863.14981.370.camel@yam-132-YW-E178-FTW> (raw)
In-Reply-To: <54EC466B.5060902@redhat.com>

Dear Sourceware Overseers,

I'd like to get write access to the Binutils/GDB project on sourceware.
I already do have an (write access enabled) account olegendo@gcc.gnu.org

See also the original thread:
https://sourceware.org/ml/binutils/2015-02/msg00204.html

Thanks,
Oleg

On Tue, 2015-02-24 at 09:37 +0000, Nicholas Clifton wrote:
> Hi Oleg,
> 
> >> Note that if you already have an account on sourceware.org or
> >> gcc.gnu.org for source control write access for some other project,
> >> then do not use this form. Instead send an email to the overseers mail
> >> account at this site telling what project you want write access to and
> >> who approved that access.
> >
> > I already do have an account at gcc.gnu.org (olegendo@gcc.gnu.org), i.e.
> > also write access to the GCC sources etc.  According to the page, I
> > should not fill out the form.  So who's going to help with this?
> 
> OK, so just send an email to: overseers@sourceware.org asking for write 
> access to the Binutils project.  You can say that both Kaz and I are 
> recommending this, in case they want a referral.
> 
> Cheers
>    Nick
> 


       reply	other threads:[~2015-02-24 10:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1423917696.18129.45.camel@yam-132-YW-E178-FTW>
     [not found] ` <20150214.220943.231145352.kkojima@rr.iij4u.or.jp>
     [not found]   ` <1423919554.18129.47.camel@yam-132-YW-E178-FTW>
     [not found]     ` <20150214.224141.334659530.kkojima@rr.iij4u.or.jp>
     [not found]       ` <54EB61FC.4000607@redhat.com>
     [not found]         ` <1424729272.14981.364.camel@yam-132-YW-E178-FTW>
     [not found]           ` <54EC466B.5060902@redhat.com>
2015-02-24 10:14             ` Oleg Endo [this message]
2015-02-25 13:14               ` Ian Lance Taylor
2023-08-09 16:21 Binutils " Richard Ball
2023-08-09 22:34 ` Mark Wielaard
  -- strict thread matches above, loose matches on Subject: below --
2020-05-26  5:37 Stefan Schulze Frielinghaus
2020-05-26 14:50 ` Christopher Faylor
2020-05-26 15:35   ` Stefan Schulze Frielinghaus
2020-05-18 19:12 Stefan Schulze Frielinghaus
2020-05-18 19:59 ` Christopher Faylor
2017-05-15 13:23 Adhemerval Zanella
2017-05-15 14:48 ` Maxim Kuvyrkov
2017-05-16 14:42 ` Frank Ch. Eigler
2016-03-08  1:14 binutils " Trevor Saunders
2016-03-08  1:48 ` Frank Ch. Eigler
2015-07-24  7:56 Binutils " Robert Suchanek
2015-07-25  0:20 ` Ian Lance Taylor
2011-11-29 19:49 binutils " Andrew Pinski
2011-11-29 20:06 ` Christopher Faylor
2000-12-30  6:08 Ulrich Drepper
2000-04-04 13:38 ` Ulrich Drepper
2000-12-30  6:08 ` Ian Lance Taylor
2000-04-04 13:45   ` Ian Lance Taylor
2000-12-30  6:08   ` Ulrich Drepper
2000-04-04 13:59     ` Ulrich Drepper

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=1424772863.14981.370.camel@yam-132-YW-E178-FTW \
    --to=oleg.endo@t-online.de \
    --cc=kkojima@rr.iij4u.or.jp \
    --cc=nickc@redhat.com \
    --cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).