From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: overseers@sourceware.org, Corinna Vinschen <vinschen@redhat.com>
Subject: Re: Write-access to Newlib
Date: Wed, 07 Jun 2017 12:40:00 -0000 [thread overview]
Message-ID: <b53e0386-369f-65bd-2d6e-e36e14aef244@embedded-brains.de> (raw)
In-Reply-To: <20170607122954.GA19192@redhat.com>
Hello,
On 07/06/17 14:29, Frank Ch. Eigler wrote:
> Hi -
>
>> I would like to get write-access to Newlib for my account
>> sh@gcc.gnu.org. It was approved by Corinna Vinschen.
> Done.
I have:
git remote -v
upstream ssh://sh@sourceware.org/git/newlib-cygwin.git (fetch)
upstream ssh://sh@sourceware.org/git/newlib-cygwin.git (push)
I get:
git push upstream master:master
Counting objects: 4, done.
Delta compression using up to 12 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 426 bytes | 0 bytes/s, done.
Total 4 (delta 3), reused 0 (delta 0)
error: insufficient permission for adding an object to repository
database ./objects
fatal: failed to write object
error: remote unpack failed: unpack-objects abnormal exit
To ssh://sourceware.org/git/newlib-cygwin.git
! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to
'ssh://sh@sourceware.org/git/newlib-cygwin.git'
I can pull with this account, so read-only works.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
next prev parent reply other threads:[~2017-06-07 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 10:49 Sebastian Huber
2017-06-07 10:54 ` Corinna Vinschen
2017-06-07 12:29 ` Frank Ch. Eigler
2017-06-07 12:40 ` Sebastian Huber [this message]
2017-06-07 12:47 ` Frank Ch. Eigler
2017-06-07 12:50 ` Sebastian Huber
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=b53e0386-369f-65bd-2d6e-e36e14aef244@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
--cc=vinschen@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).