From: Junio C Hamano <gitster@pobox.com>
To: Stefan Naewe <stefan.naewe@atlas-elektronik.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] urls.txt: document optional port specification in git URLS
Date: Wed, 04 Feb 2009 10:09:27 -0800 [thread overview]
Message-ID: <7vr62et6p4.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1233748295-4554-1-git-send-email-stefan.naewe@atlas-elektronik.com> (Stefan Naewe's message of "Wed, 4 Feb 2009 12:51:35 +0100")
Stefan Naewe <stefan.naewe@atlas-elektronik.com> writes:
> Signed-off-by: Stefan Naewe <stefan.naewe@atlas-elektronik.com>
> ---
> Documentation/urls.txt | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/urls.txt b/Documentation/urls.txt
> index fa34c67..c74f00b 100644
> --- a/Documentation/urls.txt
> +++ b/Documentation/urls.txt
> @@ -8,8 +8,8 @@ to name the remote repository:
> - rsync://host.xz/path/to/repo.git/
> - http://host.xz/path/to/repo.git/
> - https://host.xz/path/to/repo.git/
> -- git://host.xz/path/to/repo.git/
> -- git://host.xz/~user/path/to/repo.git/
> +- git://host.xz{startsb}:port{endsb}/path/to/repo.git/
> +- git://host.xz{startsb}:port{endsb}/~user/path/to/repo.git/
> - ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/
> - ssh://{startsb}user@{endsb}host.xz/path/to/repo.git/
> - ssh://{startsb}user@{endsb}host.xz/~user/path/to/repo.git/
Hmph, I wonder if we want that for http:// and https://, too.
next prev parent reply other threads:[~2009-02-04 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 11:51 [PATCH] urls.txt: document optional port specification in git URLS Stefan Naewe
2009-02-04 18:09 ` Junio C Hamano [this message]
2009-02-04 20:49 ` [PATCH v2] " Stefan Naewe
2009-02-04 20:53 ` Junio C Hamano
2009-02-04 21:02 ` Stefan Näwe
2009-02-04 21:05 ` Junio C Hamano
[not found] ` <20090205080913.GB27983@ultras>
2009-02-05 8:36 ` [PATCH] " Nicolas Sebrecht
2009-02-05 9:12 ` Marius Storm-Olsen
2009-02-05 8:41 ` Stefan Naewe
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=7vr62et6p4.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=stefan.naewe@atlas-elektronik.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 NNTP newsgroup(s).