public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: Re: Request for commit access to glibc
Date: Sat, 19 Jan 2019 06:58:00 -0000	[thread overview]
Message-ID: <20190119065804.GA7703@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4497db54-1fe7-46ab-17de-3bf347bd9c00@redhat.com>

On Fri, Jan 18, 2019 at 01:51:12PM -0500, Carlos O'Donell wrote:
>Did we roll the glibc group access setup into one step?
>
>We have it as a distinct step in the glibc account setup process right now.
>
>"Becoming a maintainer (developer)"
>https://sourceware.org/glibc/wiki/MAINTAINERS#Becoming_a_maintainer_.28developer.29
>
>"Source Control ACLs"
>https://sourceware.org/glibc/wiki/MAINTAINERS#SourceControlACL

Sourceware account creation has always granted you access to the project
for requested project.  sourceware accounts are only for source control
access so providing an account with no attached project wouldn't make
any sense.

The only time that follow-on email to overseers is required is when you
are requesting access to additional project other than the one mentioned
in the initial account creation, e.g., when you have a glibc account and
want additional write access to gcc.

cgf

      reply	other threads:[~2019-01-19  6:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18  1:37 Feng Xue
2019-01-18  4:05 ` Christopher Faylor
2019-01-18  9:17   ` Feng Xue
2019-01-18 18:51     ` Carlos O'Donell
2019-01-19  6:58       ` Christopher Faylor [this message]

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=20190119065804.GA7703@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=carlos@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).