public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: "Frank Ch. Eigler" <fche@redhat.com>,
	overseers@sources.redhat.com, nickc@redhat.com,
	David Daney <ddaney@avtrex.com>,
	Eric Christopher <echristo@redhat.com>
Subject: Re: New Patch to fix MIPS -mno-shared with multi-got...
Date: Wed, 16 Mar 2005 16:45:00 -0000	[thread overview]
Message-ID: <20050305020811.GA26809@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20050305020214.GA28932@redhat.com>

On Fri, Mar 04, 2005 at 09:02:14PM -0500, Frank Ch. Eigler wrote:
>On Fri, Mar 04, 2005 at 04:09:30PM -0800, Eric Christopher wrote:
>>On Fri, 2005-03-04 at 15:52 -0800, David Daney wrote:
>>>Eric Christopher wrote:
>>>>>Oh no!  I guess I do not have write access.
>>>>>
>>>>>I just got:
>>>>>Checking in bfd/ChangeLog;
>>>>>/cvs/src/src/bfd/ChangeLog,v  <--  ChangeLog
>>>>>new revision: 1.2949; previous revision: 1.2948
>>>>>cvs [commit aborted]: could not open lock file 
>>>>>`/cvs/src/src/bfd/,ChangeLog,': Permission denied
>>>>>
>>>> 
>>>> 
>>>> I'll sponsor your write access for binutils.
>>> 
>>> How long does that take to turn on?
>>> 
>>> Note that :ext:daney@sourceware.org:/cvs/src works for read access so 
>>> sourceware.org must already have my ssh public key.
>>> 
>>> My copyright assignment is in order for binutils as well.
>>
>>Good question.
>>
>>Overseers?
>>
>>On Fri, Mar 04, 2005 at 04:09:30PM -0800, Eric Christopher forwarded:
>>> > >>Oh no!  I guess I do not have write access.
>>> > > I'll sponsor your write access for binutils.
>>> > How long does that take to turn on?
>>> [...]
>>
>>... about 60 seconds after receiving the request.  This is done.

Isn't Nick Clifton supposed to approve access to bfd?

cgf

  reply	other threads:[~2005-03-05  2:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42277C17.7030608@avtrex.com>
     [not found] ` <87r7iw2yfp.fsf@firetop.home>
     [not found]   ` <422790D1.8010408@avtrex.com>
     [not found]     ` <20050303224853.GO1272@rembrandt.csv.ica.uni-stuttgart.de>
     [not found]       ` <4227A450.3030800@avtrex.com>
     [not found]         ` <87k6onn470.fsf@firetop.home>
     [not found]           ` <4228BA29.3010804@avtrex.com>
     [not found]             ` <20050304194533.GA5478@nevyn.them.org>
     [not found]               ` <4228D8E8.1040803@avtrex.com>
     [not found]                 ` <20050304221148.GA17078@hattusa.textio>
     [not found]                   ` <4228DF63.2010700@avtrex.com>
     [not found]                     ` <1109979615.6825.1.camel@localhost.localdomain>
     [not found]                       ` <4228F4B4.5050805@avtrex.com>
2005-03-09  0:55                         ` Eric Christopher
2005-03-16 16:34                           ` Frank Ch. Eigler
2005-03-16 16:45                             ` Christopher Faylor [this message]
2005-03-16 19:10                               ` Nick Clifton
2005-03-16 17:10                             ` Eric Christopher

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=20050305020811.GA26809@trixie.casa.cgf.cx \
    --to=me@cgf.cx \
    --cc=ddaney@avtrex.com \
    --cc=echristo@redhat.com \
    --cc=fche@redhat.com \
    --cc=nickc@redhat.com \
    --cc=overseers@sources.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).