Re: [PATCH 2/3] clone: make --local handle URLs
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- May 28, 2012, 18:31 UTC
- Message-ID
- <4FC3C46D.5070704@kdbg.org>
- In-Reply-To
- <20120526034532.GB14332@sigill.intra.peff.net>
Am 26.05.2012 05:45, schrieb Jeff King:
> And did you know that file:// URLs > can have a hostname in them? How useless.
...
Show 14 quoted lines
> +test_expect_success 'cloning file:// turns off local optimizations' ' > + git clone --bare file://"$PWD"/a non-local && > + ! repo_is_hardlinked non-local > +' > + > +test_expect_success 'cloning file:// with --local uses hardlinks' ' > + git clone --bare --local file://"$PWD"/a force-local && > + repo_is_hardlinked force-local > +' > + > +test_expect_success 'cloning file:// with --local parses URL properly' ' > + git clone --bare --local file://host/"$PWD"/%61 force-local-odd && > + repo_is_hardlinked force-local-odd > +'
I'm pretty certain that we must use file://c:/path/to/repo on Windows to make these work. This means we need $(pwd) rather than $PWD. But what does this mean w.r.t. parsing the URL in the strict sense? Is "c:" the host part?
-- Hannes