From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>, hjl.tools@gmail.com
Subject: Re: Request from Vladimir Mezentsev
Date: Fri, 8 Apr 2022 09:17:59 -0700 [thread overview]
Message-ID: <3ee13339-b82e-b176-0f85-6e28c2925caa@oracle.com> (raw)
In-Reply-To: <Yk+AwkbVg0jPIGXo@elastic.org>
On 4/7/22 17:24, Frank Ch. Eigler wrote:
>> Now:
>> % git push sourceware vmezents/zlib:master
>> vmezentsev@sourceware.org: Permission denied (publickey).
>> fatal: Could not read from remote repository.
> Your userid at sourceware is: vmezents .
>
Thank you !
I made my first push:
% git push sourceware vmezents/zlib:master
Enumerating objects: 35, done.
Counting objects: 100% (35/35), done.
Delta compression using up to 68 threads
Compressing objects: 100% (20/20), done.
Writing objects: 100% (20/20), 3.17 KiB | 44.00 KiB/s, done.
Total 20 (delta 16), reused 0 (delta 0), pack-reused 0
To ssh://sourceware.org/git/binutils-gdb.git
6849c6a2b8f..9f184a64f51 vmezents/zlib -> master
-Vladimir
next prev parent reply other threads:[~2022-04-08 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 18:58 vladimir.mezentsev
2022-03-22 19:18 ` H.J. Lu
2022-03-23 0:38 ` Christopher Faylor
2022-04-05 21:03 ` Vladimir Mezentsev
2022-04-05 23:00 ` Christopher Faylor
2022-04-05 23:22 ` Vladimir Mezentsev
2022-04-06 19:37 ` Frank Ch. Eigler
2022-04-07 17:59 ` Vladimir Mezentsev
2022-04-07 18:02 ` Frank Ch. Eigler
2022-04-07 19:13 ` Vladimir Mezentsev
2022-04-07 19:21 ` Frank Ch. Eigler
2022-04-07 21:31 ` Vladimir Mezentsev
2022-04-08 0:24 ` Frank Ch. Eigler
2022-04-08 16:17 ` Vladimir Mezentsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-23 21:44 vladimir.mezentsev
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=3ee13339-b82e-b176-0f85-6e28c2925caa@oracle.com \
--to=vladimir.mezentsev@oracle.com \
--cc=fche@elastic.org \
--cc=hjl.tools@gmail.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).