From: Junio C Hamano <junkio@cox.net>
To: Alp Toker <alp@atoker.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix ssh:// URLs in generated documentation
Date: Wed, 12 Jul 2006 21:58:50 -0700 [thread overview]
Message-ID: <7vpsgaw16d.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <11527413212127-git-send-email-alp@atoker.com> (Alp Toker's message of "Wed, 12 Jul 2006 22:55:21 +0100")
Alp Toker <alp@atoker.com> writes:
> Commit c3f17061be95de3498449a548e93883aebff23d6 was causing warnings
> during doc generation due to bad asciidoc markup.
>
> This resulted in "ssh://[user@]host.xz/path/to/repo.git/" being rendered
> as "host.xz/path/to/repo.git/" in the man pages and html output.
I wonder if this is with less formatting impact then.
diff --git a/Documentation/urls.txt b/Documentation/urls.txt
index 9abec80..93378d2 100644
--- a/Documentation/urls.txt
+++ b/Documentation/urls.txt
@@ -10,9 +10,9 @@ to name the remote repository:
- https://host.xz/path/to/repo.git/
- git://host.xz/path/to/repo.git/
- git://host.xz/~user/path/to/repo.git/
-- ssh://[user@]host.xz/path/to/repo.git/
-- ssh://[user@]host.xz/~user/path/to/repo.git/
-- ssh://[user@]host.xz/~/path/to/repo.git
+- ssh://+++[user@+++]host.xz/path/to/repo.git/
+- ssh://+++[user@+++]host.xz/~user/path/to/repo.git/
+- ssh://+++[user@+++]host.xz/~/path/to/repo.git
===============================================================
SSH Is the default transport protocol and also supports an
next prev parent reply other threads:[~2006-07-13 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 21:55 [PATCH] Documentation: Fix ssh:// URLs in generated documentation Alp Toker
2006-07-13 4:58 ` Junio C Hamano [this message]
2006-07-13 5:48 ` Alp Toker
-- strict thread matches above, loose matches on Subject: below --
2006-07-14 10:24 [PATCH] Revert "Documentation: Fix ssh://[user@]host.xz URL" Alp Toker
2006-07-14 10:24 ` [PATCH] Documentation: Fix ssh:// URLs in generated documentation Alp Toker
2006-07-14 21:46 ` 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=7vpsgaw16d.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=alp@atoker.com \
--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;
as well as URLs for NNTP newsgroup(s).