From: Michael J Gruber <git@drmicha.warpmail.net>
To: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
Cc: git@vger.kernel.org
Subject: Re: can not clone via git:// anymore
Date: Wed, 04 Mar 2009 13:59:15 +0100 [thread overview]
Message-ID: <49AE7B23.1070008@drmicha.warpmail.net> (raw)
In-Reply-To: <49AE64F2.1090405@cetrtapot.si>
Hinko Kocevar venit, vidit, dixit 04.03.2009 12:24:
> Hi,
>
> I've recently discovered that my GIT repository is not letting me clone it via git clone git://.
> It works using git clone git@.. (SSH) but with GIT protocol..
>
> Here is the case:
> hinkok@alala /tmp $ git --version
> git version 1.6.0.6
> hinkok@alala /tmp $ git clone git://zidar/sdk.git
> Initialized empty Git repository in /tmp/sdk/.git/
> fatal: The remote end hung up unexpectedly
>
> My earlier clone (few months old) has this in .git/config:
> hinkok@alala /work/git/sdk.git $ cat .git/config
> [core]
> repositoryformatversion = 0
> filemode = true
> bare = false
> logallrefupdates = true
> [remote "origin"]
> url = git@zidar:repositories/sdk.git
> fetch = +refs/heads/*:refs/remotes/origin/*
> [branch "master"]
> remote = origin
> merge = refs/heads/master
>
>
> But I remember cloning via SSH that time, because I needed git push to work,
> but now other developer do not need the SSH access, but only GIT read-only -
> they can only clone, not push.
>
> I do not administer the server git repos is located on, so I must have some
> information before I attack the admin..
Sorry in case this is trivial, but has git: access ever worked? It
requires a git daemon running on the server, whereas ssh access does not
require that. git@zidar:repositories/sdk.git uses ssh access.
Michael
next prev parent reply other threads:[~2009-03-04 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 11:24 can not clone via git:// anymore Hinko Kocevar
2009-03-04 12:59 ` Michael J Gruber [this message]
2009-03-04 13:28 ` Hinko Kocevar
2009-03-04 14:24 ` Jeff King
2009-03-05 9:16 ` Hinko Kocevar
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=49AE7B23.1070008@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=hinko.kocevar@cetrtapot.si \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.