From: Petr Baudis <pasky@suse.cz>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org
Subject: Re: FEATURE REQUEST: Allow SSH style URLS (with extra colon)
Date: Sat, 30 Jan 2010 23:21:57 +0100 [thread overview]
Message-ID: <20100130222157.GI9553@machine.or.cz> (raw)
In-Reply-To: <87tyu3cyy3.fsf@jondo.cante.net>
On Sat, Jan 30, 2010 at 06:57:56PM +0200, Jari Aalto wrote:
>
> According to git-clone[1] the SSH protocol is specied as:
>
> ssh://[user@]host.xz[:port]/path
>
> It woudl be nice if the ":" were allowed, so that the familiar SSH style
> patch notation could be used, making the spec:
>
> ssh://[user@]host.xz[:[port]]/path
>
> An example:
>
> ssh://foo@examplecom:/path
> |
> Allowed
But that's not an URL anymore. If you want to use ssh pathspec, write it
as a pathspec, not an URL. Just foo@example.com:/path works fine. ;-)
Petr "Pasky" Baudis
next prev parent reply other threads:[~2010-01-30 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 16:57 FEATURE REQUEST: Allow SSH style URLS (with extra colon) Jari Aalto
2010-01-30 17:27 ` Ilari Liusvaara
2010-01-30 22:21 ` Petr Baudis [this message]
2010-01-30 22:30 ` Junio C Hamano
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=20100130222157.GI9553@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
/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 NNTP newsgroup(s).