From: Christopher Faylor <me@cgf.cx>
To: overseers@sourceware.org, 'Jeff Johnston' <jjohnstn@redhat.com>,
Eric Blake <ebb9@byu.net>
Subject: Re: newlib write access
Date: Tue, 10 Apr 2007 05:02:00 -0000 [thread overview]
Message-ID: <20070410050200.GA10880@ednor.casa.cgf.cx> (raw)
In-Reply-To: <461AF6C5.7030900@byu.net>
On Mon, Apr 09, 2007 at 08:30:29PM -0600, Eric Blake wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>According to Jeff Johnston on 4/9/2007 9:55 AM:
>>>> Sure, this matches what glibc does. Please apply if your testing was
>>>> successful.
>>>
>>> I have an account on sourceware.org (ericb), but currently do not have
>>> write access to the newlib repository:
>>>
>>> Checking in ChangeLog;
>>> /cvs/src/src/newlib/ChangeLog,v <-- ChangeLog
>>> new revision: 1.1001; previous revision: 1.1000
>>> cvs [commit aborted]: could not open lock file
>>> `/cvs/src/src/newlib/,ChangeLog,': Permission denied
>>>
>>> Do you want to grant that to me, or just check this in on my behalf?
>>>
>>
>> I personally can't grant you access. That's up to the Robot Elders
>> (also known as the overseers list :) )
>
>So, kind robots, may I be granted write access to the newlib repository? :)
I am not a robot. I am a human being.
I've added you to the group which should allow you to checkin to newlib.
cgf
*beep*
prev parent reply other threads:[~2007-04-10 5:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <loom.20070405T164416-400@post.gmane.org>
[not found] ` <46151DFF.3060009@redhat.com>
[not found] ` <46185A1F.2050406@byu.net>
[not found] ` <461A61DD.4080105@redhat.com>
2007-04-10 2:30 ` Eric Blake
2007-04-10 5:02 ` 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=20070410050200.GA10880@ednor.casa.cgf.cx \
--to=me@cgf.cx \
--cc=ebb9@byu.net \
--cc=jjohnstn@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).