Torsten Bögershausen tbo...@web.de writes:
So I think that git clone can be slighty more consistant here.
Sure.
I _think_ taking notice of word:// (with doubled slashes) and
treating it specially will not introduce any new issue; while it is
still OK for users to have a local directory
On 2015-08-06 09.50, Junio C Hamano wrote:
Junio C Hamano gits...@pobox.com writes:
Torsten Bögershausen tbo...@web.de writes:
It looks as if
static char *get_repo_path(const char *repo, int *is_bundle)
in built/clone.c
checks if there is a local directory structure looking like a
.git
Junio C Hamano gits...@pobox.com writes:
Torsten Bögershausen tbo...@web.de writes:
It looks as if
static char *get_repo_path(const char *repo, int *is_bundle)
in built/clone.c
checks if there is a local directory structure looking like a
.git directory.
This is wrong.
It is as
Torsten Bögershausen tbo...@web.de writes:
It looks as if
static char *get_repo_path(const char *repo, int *is_bundle)
in built/clone.c
checks if there is a local directory structure looking like a
.git directory.
This is wrong.
It is as designed, though, to allow cloning from a local
Hi All,
A developer at $dayjob called me over to have a look at a git error he
was getting (names changed to protect the innocent).
$ git --version
git version 2.5.0
$ git clone ssh://example.com/repo.git
Cloning into 'repo'...
fatal: I don't handle protocol '/home/user/src/ssh'
After
On 2015-08-06 06.21, Chris Packham wrote:
Hi All,
A developer at $dayjob called me over to have a look at a git error he
was getting (names changed to protect the innocent).
$ git --version
git version 2.5.0
$ git clone ssh://example.com/repo.git
Cloning into 'repo'...
fatal:
6 matches
Mail list logo
