From: Chris Packham <judge.packham@gmail.com>
To: GIT <git@vger.kernel.org>
Subject: Error when cloning with weird local directory
Date: Thu, 6 Aug 2015 16:21:06 +1200 [thread overview]
Message-ID: <CAFOYHZByteuPZwRvw9tzFWOD6vguw4wPK1J6rLZZvHzyZRBtSA@mail.gmail.com> (raw)
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 a bit of head scratching we found that he had a local directory
structure called 'ssh://example.com/repo.git' it wasn't a complete
repo but it had some of the things one expects to find in a .git
directory (info, objects, refs, etc). It had been there for a while
and we suspect was created by a scp gone wrong from the last time he
was dealing with repo.git.
I'm wondering if it's worth catching this kind of weirdness and
erroring out with a slightly more useful message. I'm also wondering
what would have happened if this repo was actually a full and complete
thing.
I'm not sure that there is a problem worth solving here. I can provide
an anonymized tarball of the directory structure in question if anyone
is interested. But maybe this is useful for future mailing list
searchers[1].
Thanks,
Chris
--
[1] - https://xkcd.com/979/
next reply other threads:[~2015-08-06 4:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 4:21 Chris Packham [this message]
2015-08-06 5:48 ` Error when cloning with weird local directory Torsten Bögershausen
2015-08-06 7:44 ` Junio C Hamano
2015-08-06 7:50 ` Junio C Hamano
2015-08-08 6:26 ` Torsten Bögershausen
2015-08-10 18:16 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFOYHZByteuPZwRvw9tzFWOD6vguw4wPK1J6rLZZvHzyZRBtSA@mail.gmail.com \
--to=judge.packham@gmail.com \
--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.
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 NNTP newsgroup(s).