From: Alp Toker <alp@atoker.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix ssh:// URLs in generated documentation
Date: Thu, 13 Jul 2006 06:48:58 +0100 [thread overview]
Message-ID: <44B5DECA.8040401@atoker.com> (raw)
In-Reply-To: <7vpsgaw16d.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> 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
Your call. I almost went that way but decided the more invasive patch
left the source a bit more readable as it didn't need escaping. As long
as the output gets fixed, nobody will be losing sleep over this one.
next prev parent reply other threads:[~2006-07-13 5:49 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
2006-07-13 5:48 ` Alp Toker [this message]
-- 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=44B5DECA.8040401@atoker.com \
--to=alp@atoker.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).