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 21:04:00 -0000	[thread overview]
Message-ID: <ab50bbf1-ea31-4dd8-2b03-cbfff1a2732c@redhat.com> (raw)
In-Reply-To: <CAKmqyKNwLO=JoKQbYApktOQFJcdeOzavW8E2EQjqCOHfhYi3=A@mail.gmail.com>

On 9/25/19 4:40 PM, Alistair Francis wrote:
> On Wed, Sep 25, 2019 at 1:08 PM Carlos O'Donell <carlos@redhat.com> wrote:
>> Tweaked. Please review?
>>
>> https://sourceware.org/glibc/wiki/MAINTAINERS#Becoming_a_maintainer_.28developer.29
> 
> That is clearer.
> 
> Maybe it's worth adding a note about people who already have accounts
> and want to join a new project?

Clarified a bit.

"* Individual developers, without an existing account, ..."

And so you should naturally go to the last bullet:

"* If you have an existing account you must..."

-- 
Cheers,
Carlos.

  reply	other threads:[~2019-09-25 21:04 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
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 [this message]
  -- 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=ab50bbf1-ea31-4dd8-2b03-cbfff1a2732c@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).