{"thread":{"id":"23239","subject":"[PATCH v2] Documentation/urls: Rewrite to accomodate ::
","startedAt":"2010-03-29T16:59:29Z","lastAt":"2010-04-04T22:33:34Z","messageCount":3,"participants":["Ramkumar Ramachandra","Ilari Liusvaara"],"isPatch":true,"patchVersion":2,"patchTotal":null},"messages":[{"id":"138113","messageId":"f3271551003290959v263fe04bt1047f390788916c2@mail.gmail.com","threadId":"23239","inReplyTo":null,"subject":"[PATCH v2] Documentation/urls: Rewrite to accomodate ::
","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2010-03-29T16:59:29Z","receivedAt":"2010-03-29T16:59:29Z","isPatch":true,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"Rewrite the first part of the document to explicitly show differences\nbetween the URLs that can be used with different transport\nprotocols. Mention ::
format to explicitly invoke\na remote helper.\n---\n Complete rewrite since v1. Ilari's review mentioned that
\n can be anything, depending on the remote helper used. Removed\n redundancy and clarified rest of document so that this fact isn't\n confusing.\n\n Documentation/urls.txt | 58 +++++++++++++++++++++++------------------------\n 1 files changed, 28 insertions(+), 30 deletions(-)\n\ndiff --git a/Documentation/urls.txt b/Documentation/urls.txt\nindex 459a394..262c729 100644\n--- a/Documentation/urls.txt\n+++ b/Documentation/urls.txt\n@@ -1,44 +1,42 @@\n GIT URLS[[URLS]]\n ----------------\n\n-One of the following notations can be used\n-to name the remote repository:\n-\n-- rsync://host.xz/path/to/repo.git/\n-- http://host.xz{startsb}:port{endsb}/path/to/repo.git/\n-- https://host.xz{startsb}:port{endsb}/path/to/repo.git/\n-- git://host.xz{startsb}:port{endsb}/path/to/repo.git/\n-- git://host.xz{startsb}:port{endsb}/~user/path/to/repo.git/\n-- ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/\n-- ssh://{startsb}user@{endsb}host.xz/path/to/repo.git/\n-- ssh://{startsb}user@{endsb}host.xz/~user/path/to/repo.git/\n-- ssh://{startsb}user@{endsb}host.xz/~/path/to/repo.git\n-\n-SSH is the default transport protocol over the network. You can\n-optionally specify which user to log-in as, and an alternate,\n-scp-like syntax is also supported. Both syntaxes support\n-username expansion, as does the native git protocol, but\n-only the former supports port specification. The following\n-three are identical to the last three above, respectively:\n-\n-- {startsb}user@{endsb}host.xz:/path/to/repo.git/\n-- {startsb}user@{endsb}host.xz:~user/path/to/repo.git/\n+In general, URLs contain information about the transport protocol, the\n+address of the remote server and the path to the repository. Depending\n+on the transport protocol, some of these may be omitted.\n+\n+SSH is the default transport protocol over the network, which allows\n+optional username and port specification. An alternate scp-like syntax\n+is also supported, and both syntaxes support username expansion.\n+\n+- ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git\n - {startsb}user@{endsb}host.xz:path/to/repo.git\n\n-To sync with a local directory, you can use:\n+The native git, rsync, http, and https transport helpers support the\n+following syntaxes:\n+\n+- git://host.xz{startsb}:port{endsb}/path/to/repo.git\n+- rsync://host.xz/path/to/repo.git\n+- http://host.xz{startsb}:port{endsb}/path/to/repo.git\n+- https://host.xz{startsb}:port{endsb}/path/to/repo.git\n\n-- /path/to/repo.git/\n-- file:///path/to/repo.git/\n+For local respositories, the following syntaxes are supported:\n+\n+- /path/to/repo.git\n+- file:///path/to/repo.git\n\n ifndef::git-clone[]\n-They are mostly equivalent, except when cloning. See\n-linkgit:git-clone[1] for details.\n+They are mostly equivalent, except when cloning, when the former\n+implies --local option. See linkgit:git-clone[1] for details.\n endif::git-clone[]\n\n-ifdef::git-clone[]\n-They are equivalent, except the former implies --local option.\n-endif::git-clone[]\n+To explicity request a remote helper for a certain transport protocol,\n+you can use:\n+\n+- ::
\n\n+where
may be a path, a server and path, or something else\n+depending on the remote helper.\n\n If there are a large number of similarly-named remote repositories and\n you want to use a different format for them (such that the URLs you\n-- \n1.7.0.3\n"},{"id":"138551","messageId":"k2hf3271551004041227sfade965aubb4273a6340b7518@mail.gmail.com","threadId":"23239","inReplyTo":"f3271551003290959v263fe04bt1047f390788916c2@mail.gmail.com","subject":"Re: [PATCH v2] Documentation/urls: Rewrite to accomodate ::
","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2010-04-04T19:27:13Z","receivedAt":"2010-04-04T19:27:13Z","isPatch":true,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"On Mon, Mar 29, 2010 at 10:29 PM, Ramkumar Ramachandra\n wrote:\n> Rewrite the first part of the document to explicitly show differences\n> between the URLs that can be used with different transport\n> protocols. Mention ::
format to explicitly invoke\n> a remote helper.\n\nCould someone remote helper experts kindly review/ ack this?\n\nI forgot to sign off:\nSigned-off-by: Ramkumar Ramachandra \n\nThanks!\n-- Ram\n"},{"id":"138568","messageId":"20100404223334.GA23049@LK-Perkele-V2.elisa-laajakaista.fi","threadId":"23239","inReplyTo":"k2hf3271551004041227sfade965aubb4273a6340b7518@mail.gmail.com","subject":"Re: [PATCH v2] Documentation/urls: Rewrite to accomodate ::
","fromName":"Ilari Liusvaara","fromEmail":"ilari.liusvaara@elisanet.fi","sentAt":"2010-04-04T22:33:34Z","receivedAt":"2010-04-04T22:33:34Z","isPatch":true,"sender":{"key":"ilari.liusvaara@elisanet.fi","avatar":null},"body":"On Mon, Apr 05, 2010 at 12:57:13AM +0530, Ramkumar Ramachandra wrote:\n> On Mon, Mar 29, 2010 at 10:29 PM, Ramkumar Ramachandra\n> wrote:\n> > Rewrite the first part of the document to explicitly show differences\n> > between the URLs that can be used with different transport\n> > protocols. Mention ::
format to explicitly invoke\n> > a remote helper.\n> \n> Could someone remote helper experts kindly review/ ack this?\n\nSome things from quick reading.\n\n:// also requests transport helper remote-\nif is not known internally. Then there is ftp and ftps...\n\n-Ilari\n"}]}