list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: "Johannes Schindelin via GitGitGadget" <>
Cc: Johannes Schindelin <>,
	Johannes Schindelin <>
Subject: [PATCH] t5580: test cloning without file://, test fetching via UNC paths
Date: Thu, 13 Feb 2020 21:51:44 +0000
Message-ID: <> (raw)

From: Johannes Schindelin <>

On Windows, it is quite common to work with network drives. The format
of the paths to network drives (or "network shares", or UNC paths) is:


We already have a couple regression tests revolving around those types
of paths, but we missed cloning and fetching from UNC paths without
leading `file://` (and with backslashes instead of forward slashes).
This lil' patch closes that gap.

It gets a bit silly to add the commands to the name of the test script,
so let's just rename it while we're testing more UNC stuff.

Signed-off-by: Johannes Schindelin <>
    Add more regression tests around fetching/cloning from UNC paths
    On Windows, we want to make sure that we can fetch and clone from
    network drives. Let's add regression tests to make sure about that.

Fetch-It-Via: git fetch pr-143/dscho/test-unc-fetch-v1

 t/{ =>} | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 rename t/{ =>} (89%)

diff --git a/t/ b/t/
similarity index 89%
rename from t/
rename to t/
index 01b52c195a..cf768b3a27 100755
--- a/t/
+++ b/t/
@@ -40,11 +40,23 @@ test_expect_success clone '
 	git clone "file://$UNCPATH" clone
+test_expect_success 'clone without file://' '
+	git clone "$UNCPATH" clone-without-file
 test_expect_success 'clone with backslashed path' '
 	BACKSLASHED="$(echo "$UNCPATH" | tr / \\\\)" &&
 	git clone "$BACKSLASHED" backslashed
+test_expect_success fetch '
+	git init to-fetch &&
+	(
+		cd to-fetch &&
+		git fetch "$UNCPATH" master
+	)
 test_expect_success push '
 		cd clone &&

base-commit: d8437c57fa0752716dde2d3747e7c22bf7ce2e41

                 reply	other threads:[~2020-02-13 21:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone