From: Caroline Tice <cmtice@google.com>
To: overseers@sourceware.org, Caroline Tice <cmtice@google.com>,
Tom Tromey <tromey@adacore.com>
Subject: Re: Request from Caroline Tice
Date: Thu, 6 Aug 2020 16:51:37 -0700 [thread overview]
Message-ID: <CABtf2+SMO-dH0w4pe4HR+vrK2gK_6+6+XcsNoobRKNLktg+=Zw@mail.gmail.com> (raw)
In-Reply-To: <20200729194140.GA24349@cgf.cx>
I can't seem to check out a read-write version of GDB:
$ git clone ssh://sourceware.org/git/binutils-gdb.git
Cloning into 'binutils-gdb'...
Warning: Permanently added
'sourceware.org,2620:52:3:1:0:246e:9693:128c' (ECDSA) to the list of
known hosts.
cmtice@sourceware.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
$
So something with my GDB permissions is not correct...
-- Caroline
cmtice@google.com
On Wed, Jul 29, 2020 at 12:41 PM Christopher Faylor
<cgf-use-the-mailinglist-please@sourceware.org> wrote:
>
> On Wed, Jul 29, 2020 at 07:24:02PM +0000, cmtice--- via Overseers wrote:
> >Caroline Tice is requesting an account:
> >
> >Login: cmtice
> >Email: cmtice@google.com
> >Project: gdb
> >Approver: tromey@adacore.com
> >
> >Create with:
> >qcreate-user cmtice
> >
> >http://sourceware.org/cgi-bin/pdw/details.cgi?file=8695601.1482836
>
> You already have an account with write privileges to both gcc and gdb.
>
next prev parent reply other threads:[~2020-08-06 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 19:24 cmtice
2020-07-29 19:41 ` Christopher Faylor
2020-08-06 23:51 ` Caroline Tice [this message]
2020-08-06 23:57 ` Caroline Tice
2020-08-06 23:58 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 23:34 ctice
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='CABtf2+SMO-dH0w4pe4HR+vrK2gK_6+6+XcsNoobRKNLktg+=Zw@mail.gmail.com' \
--to=cmtice@google.com \
--cc=overseers@sourceware.org \
--cc=tromey@adacore.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).