From: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: SSH pull problems
Date: Sun, 05 Jun 2005 20:02:30 +0200 [thread overview]
Message-ID: <42A33E36.3060702@gorzow.mm.pl> (raw)
In-Reply-To: <Pine.LNX.4.21.0506051336440.30848-100000@iabervon.org>
Daniel Barkalow wrote:
>On Sat, 4 Jun 2005, Radoslaw Szkodzinski wrote:
>
>
>
>>I had some problems today with git+ssh protocol.
>>First, when using cg-clone, it couldn't execute cg-rpush, although it's
>>there in /usr/local.
>>Maybe that has something to do with that being added to the path in
>>/etc/profile.
>>
>>
>
>I haven't used recent Cogito, so I'm not sure, but it might actually want
>git-rpush rather than cg-rpush? Or it might be a permissions issue?
>
>
>
Make that git-rpush, I was writing from my memory, and it couldn't find
it, as in "Command not found".
It's available for all to exec, in /usr/local.
>>Second, I don't know how to specify the port number,
>>the typical notation of git+ssh://xyz:port/repo didn't work.
>>
>>
>
>I haven't made it understand port numbers yet; it should be pretty easy,
>though, if you want to do it. You'd probably have a better chance of
>getting it right than I would, if you've got an SSH server on a
>non-default port to test against. Just parse out the part of "host" after
>the : and make it a "-p" option in the execlp in rsh.c.
>
>
>
That's not a problem, I'll get to it in some short time and post a patch.
AstralStorm
next prev parent reply other threads:[~2005-06-05 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 13:05 SSH pull problems Radoslaw Szkodzinski
2005-06-05 17:47 ` Daniel Barkalow
2005-06-05 18:02 ` Radoslaw Szkodzinski [this message]
2005-06-05 17:50 ` Petr Baudis
2005-06-05 18:04 ` Radoslaw Szkodzinski
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=42A33E36.3060702@gorzow.mm.pl \
--to=astralstorm@gorzow.mm.pl \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.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