From: Michael J Gruber <git@drmicha.warpmail.net>
To: amillican <amillican@cogentsystems.com>
Cc: git@vger.kernel.org
Subject: Re: Making git work with new remote server
Date: Mon, 03 May 2010 18:14:47 +0200 [thread overview]
Message-ID: <4BDEF677.5070807@drmicha.warpmail.net> (raw)
In-Reply-To: <28436896.post@talk.nabble.com>
amillican venit, vidit, dixit 03.05.2010 17:59:
>
> 0 vote down star
>
>
> I am the CM person for a small company that just started using Git. We have
> two Git repositories currently hosted on a Windows box that is our
> all-purpose Windows server. But, we just set up a dedicated server for our
> CM software on an Ubuntu Linux server named "Callisto".
>
> So I created a test Git repository on Callisto. I gave its directory all of
> the proper permissions recursively. I had the sysadmin create a login for me
> on Callisto, and I created a key to use for logging in via SSH. I set up my
> key to use a passphrase; I don't know if that could be contributing to my
> problems? Anyway, I know my SSH login works because I tested it through
> puTTY.
>
> But, even after hours of trials and head scratching, I can't get my Windows
> Git bash (mSysGit) to talk to Callisto for the purposes of pushing or
> pulling Callisto's git repository files. Obviously, when trying a push, I've
> been trying to log into my Callisto account using SSH.
>
> I keep getting "Fatal error. The remote end hung up unexpectedly." And I've
> even gotten the error that Git doesn't recognize the test repository on
> Callisto as a git repository. I read online that the "Fatal error...hung up
> unexpectedly" is usually a problem with the server connection or
> permissions. So what am I missing or overlooking here? And why doesn't a
> pull using the git:// protocol work, since that only uses read-only access?
> Group and public permissions for the git repository's directory on Callisto
> are set to read and execute, but not write.
>
> If anyone could help, I would be so grateful. Thank you.
For git:// without ssh you need a running git-daemon on the server.
For helping you more we would need the actual commands you tried and the
exact output.
Cheers,
Michael
prev parent reply other threads:[~2010-05-03 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 15:59 Making git work with new remote server amillican
2010-05-03 16:14 ` Michael J Gruber [this message]
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=4BDEF677.5070807@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=amillican@cogentsystems.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 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.