From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
Overseers mailing list <overseers@sourceware.org>
Cc: hjl.tools@gmail.com
Subject: Re: Request from Vladimir Mezentsev
Date: Thu, 7 Apr 2022 10:59:44 -0700 [thread overview]
Message-ID: <20161a64-02cb-0981-cf6a-a5145ea02f26@oracle.com> (raw)
In-Reply-To: <Yk3r/rDisYg6Nm3s@elastic.org>
On 4/6/22 12:37, Frank Ch. Eigler wrote:
> Hi -
>
>> H.J. Lu already approved:
> OK, done.
>
> - FChE
I want to make my first push to sourceware.org/git/binutils-gdb.git
I am trying to update the latest master branch in my repository:
% git pull sourceware master:master
ssh: connect to host sourceware.org port 22: Network is unreachable
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
In my .git/config:
[remote "sourceware"]
url = ssh://vmezentsev@sourceware.org/git/binutils-gdb.git
# url = https://sourceware.org/git/binutils-gdb.git
fetch = +refs/heads/*:refs/remotes/sourceware/*
If I use 'url = https://sourceware.org/git/binutils-gdb.git', I can make
`git pull`.
But how can I make `git push` ?
Thank you,
-Vladimir
next prev parent reply other threads:[~2022-04-07 17:59 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 [this message]
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
-- 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=20161a64-02cb-0981-cf6a-a5145ea02f26@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).