From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Adrien Berchet'" <adrien.berchet@gmail.com>, <git@vger.kernel.org>
Subject: RE: [bug] Cloning SSH repo into /tmp
Date: Thu, 22 Oct 2020 10:55:31 -0400 [thread overview]
Message-ID: <000601d6a883$66d8e180$348aa480$@nexbridge.com> (raw)
In-Reply-To: <CAKuTeyftpz8mQiiy2S56pxmW0fzCENAQ8=gmaTE5a-Ef5g216g@mail.gmail.com>
On October 22, 2020 6:28 AM, Adrien Berchet wrote:
> I encountered a quite weird bug when I tried to clone a repository into the
> /tmp folder (I just wanted to test something, so I was working in /tmp).
>
> I run the following command in /tmp :
> git clone ssh://[user]@[host]/project/[project_name]
> and I got the following error:
> fatal: the protocol '/tmp/ssh' is not supported
>
> I got the same result if a run the following command from /tmp directory:
> git clone ssh://[user]@[host]/project/[project_name] /tmp/project_name
>
> Nevertheless, the command works in other directories. Even the second
> command works when run from another directory (this command: git clone
> ssh://[user]@[host]/project/[project_name] /tmp/project_name).
>
> It is very specific and can easily be worked around so it is no big deal but I
> preferred reporting this in case it hides something else.
What platform are you running on? I have experienced similar when /tmp is linked to a separate file system with complex ACLs.
Regards,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next prev parent reply other threads:[~2020-10-22 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 10:28 [bug] Cloning SSH repo into /tmp Adrien Berchet
2020-10-22 14:55 ` Randall S. Becker [this message]
2020-10-22 21:27 ` Adrien Berchet
2020-10-22 22:02 ` Randall S. Becker
2020-10-23 20:49 ` Adrien Berchet
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='000601d6a883$66d8e180$348aa480$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=adrien.berchet@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.
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).