public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: overseers@sourceware.org, Alistair Francis <alistair.francis@wdc.com>
Subject: Re: glibc commit access
Date: Wed, 25 Sep 2019 16:43:00 -0000	[thread overview]
Message-ID: <d01c27db-63d7-fd30-bb77-f0056d212c59@redhat.com> (raw)
In-Reply-To: <CAKmqyKPoZoYYBwbzq29GUaw-u_xpuz6qxAhp=b3QCvSgHPL=Ng@mail.gmail.com>

On 9/25/19 12:19 PM, Alistair Francis wrote:
> On Wed, Sep 25, 2019 at 8:22 AM Carlos O'Donell <carlos@redhat.com> wrote:
>>
>> On 9/25/19 10:07 AM, Christopher Faylor wrote:
>>> On Tue, Sep 24, 2019 at 10:11:28PM -0700, Alistair Francis wrote:
>>>> Overseers,
>>>>
>>>> Please add me (alistair23) to the glibc group after verifying with
>>>> carlos@redhat.com.
>>>>
>>>> carlos@redhat.com vouches for my sanity and competence.
>>>>
>>>> I truly understand FSF copyright protocols, and always respect
>>>> per-branch policies on what I am allowed to touch and how.
>>>
>>> An account was just added for you for the glibc project yesterday.
>>
>> Perfect. Does that mean we're all done?
> 
> I'm not sure, according to
> https://sourceware.org/glibc/wiki/MAINTAINERS I still need to have
> write permission added.

You have write permission, that's what Christopher is saying above.

Having "glibc" group permission gives you write access to the glibc repo.

> Also Carlos do you mind giving me wiki edit permission and adding me
> here: https://sourceware.org/glibc/wiki/EditorGroup. My wiki name is
> AlistairFrancis

Done.

> After that I should be almost done. Thanks for your help Carlos.


-- 
Cheers,
Carlos.

  reply	other threads:[~2019-09-25 16:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25  5:12 Alistair Francis
2019-09-25 14:07 ` Christopher Faylor
2019-09-25 15:22   ` Carlos O'Donell
2019-09-25 16:24     ` Alistair Francis
2019-09-25 16:43       ` Carlos O'Donell [this message]
2019-09-25 17:50       ` Christopher Faylor
2019-09-25 20:08         ` Carlos O'Donell
2019-09-25 20:45           ` Alistair Francis
2019-09-25 21:04             ` Carlos O'Donell
  -- strict thread matches above, loose matches on Subject: below --
2013-10-09 19:53 Torvald Riegel
2013-10-09 19:55 ` Frank Ch. Eigler
2012-07-02 18:46 GLIBC " Maxim Kuvyrkov
2012-07-02 19:09 ` Roland McGrath
2012-07-09 13:23 ` Ian Lance Taylor

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=d01c27db-63d7-fd30-bb77-f0056d212c59@redhat.com \
    --to=carlos@redhat.com \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.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).