From: Jared Hance <jaredhance@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: unpack failed --- is my repos broken?
Date: Tue, 20 Jul 2010 11:35:53 -0400 [thread overview]
Message-ID: <20100720153553.GA2931@localhost.localdomain> (raw)
In-Reply-To: <4C45A7C5.1050601@llaisdy.com>
On Tue, Jul 20, 2010 at 02:42:29PM +0100, Ivan Uemlianin wrote:
> Is smart-http not entirely reliable? In which case what is the
> preferred way to communicate remotely (we need to push as well as
> pull; there are a very small number of active developers)?
I'm not entirely sure why the error is occuring, but the preferred way
to communicate is over SSH. You can use the git protocol for anonymous
pulling (but not pushing).
next prev parent reply other threads:[~2010-07-20 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 13:42 unpack failed --- is my repos broken? Ivan Uemlianin
2010-07-20 15:35 ` Jared Hance [this message]
2010-07-23 9:42 ` ssh communication not working Ivan Uemlianin
2010-07-23 10:07 ` Ilari Liusvaara
2010-07-23 10:43 ` Ivan Uemlianin
2010-07-21 16:12 ` unpack failed --- is my repos broken? Tay Ray Chuan
2010-07-23 9:38 ` Ivan Uemlianin
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=20100720153553.GA2931@localhost.localdomain \
--to=jaredhance@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).