From: Andreas Krebbel <krebbel@linux.vnet.ibm.com>
To: Andreas Jaeger <aj@suse.de>
Cc: overseers@sourceware.org, roland@hack.frob.com, roland@redhat.com
Subject: Re: Write access to glibc git repo
Date: Thu, 19 Jul 2012 10:29:00 -0000 [thread overview]
Message-ID: <5007E16F.6090202@linux.vnet.ibm.com> (raw)
In-Reply-To: <5007B185.1060607@suse.de>
On 07/19/2012 09:04 AM, Andreas Jaeger wrote:
> On 07/19/2012 08:51 AM, Andreas Krebbel wrote:
>> Overseers,
>>
>> please add the following username to the 'glibc' group:
>>
>> krebbel Andreas Krebbel IBM
>
> Andreas, is krebbel your existing sourceware account? I understand you
> have already a sourceware account used for gcc and need the additional
> permissions for glibc, correct?
Yes.
> you're the s390 maintainer, so can commit changes there without approval
> and in other areas if there's consensus about it,
Ok good. Thanks for clarifying.
-Andreas-
next prev parent reply other threads:[~2012-07-19 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 6:51 Andreas Krebbel
2012-07-19 7:05 ` Andreas Jaeger
2012-07-19 10:29 ` Andreas Krebbel [this message]
2012-07-19 12:44 ` 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=5007E16F.6090202@linux.vnet.ibm.com \
--to=krebbel@linux.vnet.ibm.com \
--cc=aj@suse.de \
--cc=overseers@sourceware.org \
--cc=roland@hack.frob.com \
--cc=roland@redhat.com \
/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).