From: Alyssa Ross <hi@alyssa.is>
To: git@vger.kernel.org
Cc: Alyssa Ross <hi@alyssa.is>
Subject: [PATCH] doc: explain why file: URLs and bundles don't mix
Date: Mon, 13 May 2019 00:23:55 +0000 [thread overview]
Message-ID: <20190513002355.25031-1-hi@alyssa.is> (raw)
Signed-off-by: Alyssa Ross <hi@alyssa.is>
---
Documentation/urls.txt | 20 +++++++++++++++-----
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/Documentation/urls.txt b/Documentation/urls.txt
index b05da95788..c83d9f859e 100644
--- a/Documentation/urls.txt
+++ b/Documentation/urls.txt
@@ -43,14 +43,24 @@ syntaxes may be used:
- \file:///path/to/repo.git/
ifndef::git-clone[]
-These two syntaxes are mostly equivalent, except when cloning, when
-the former implies --local option. See linkgit:git-clone[1] for
-details.
+These two syntaxes are mostly equivalent, with some exceptions:
+
+- When cloning, the former implies --local option. See
+ linkgit:git-clone[1] for details.
+
+- The latter is implemented using linkgit:git-upload-pack[1], which
+ expects its repository to be a directory, and therefore does not
+ work for bundles (see linkgit:git-bundle[1]).
endif::git-clone[]
ifdef::git-clone[]
-These two syntaxes are mostly equivalent, except the former implies
---local option.
+These two syntaxes are mostly equivalent, with some exceptions:
+
+- The former implies --local option.
+
+- The latter is implemented using linkgit:git-upload-pack[1], which
+ expects its repository to be a directory, and therefore does not
+ work for bundles (see linkgit:git-bundle[1]).
endif::git-clone[]
When Git doesn't know how to handle a certain transport protocol, it
--
2.21.0
next reply other threads:[~2019-05-13 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 0:23 Alyssa Ross [this message]
2019-05-13 8:05 ` [PATCH] doc: explain why file: URLs and bundles don't mix Junio C Hamano
2019-05-13 16:54 ` Alyssa Ross
2019-05-14 9:30 ` Jeff King
2019-05-14 9:29 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190513002355.25031-1-hi@alyssa.is \
--to=hi@alyssa.is \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).