From: Eric Christopher <echristo@redhat.com>
To: David Daney <ddaney@avtrex.com>
Cc: overseers@sources.redhat.com
Subject: Re: New Patch to fix MIPS -mno-shared with multi-got...
Date: Wed, 09 Mar 2005 00:55:00 -0000 [thread overview]
Message-ID: <1109981371.6825.3.camel@localhost.localdomain> (raw)
In-Reply-To: <4228F4B4.5050805@avtrex.com>
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.
> >
> > -eric
> >
>
> 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?
-eric
next parent reply other threads:[~2005-03-05 0:10 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 [this message]
2005-03-16 16:34 ` Frank Ch. Eigler
2005-03-16 16:45 ` Christopher Faylor
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=1109981371.6825.3.camel@localhost.localdomain \
--to=echristo@redhat.com \
--cc=ddaney@avtrex.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).