X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 	tests=AWL,BAYES_50,J_CHICKENPOX_31,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Message-ID: <4A212BFC.6030604@byu.net>
Date: Sat, 30 May 2009 06:52:12 -0600
From: Eric Blake <ebb9@byu.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin@cygwin.com, matthew@theiselins.net
Subject: Re: [ANNOUNCEMENT] [1.7] Updated: git-1.6.3.1-1, git{k,-gui,-completion,-svn}-1.6.3.1-1
References: <announce.4A20AB6E.1040803@byu.net> <f88ae150905300245g70761889n1d1c856847d23ea7@mail.gmail.com>
In-Reply-To: <f88ae150905300245g70761889n1d1c856847d23ea7@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[please trim what you reply to; you didn't need to repeat the attachment
verbatim]

According to Matthew Iselin on 5/30/2009 3:45 AM:
> On Sat, May 30, 2009 at 1:43 PM, Eric Blake <ebb9@byu.net> wrote:
> A new release of git, 1.6.3.1-1, has been uploaded to the cygwin 1.7
> release area.  This replaces 1.6.2.4-2 as current.
> 
> Hi,

> This version of git is still unusable for actions requiring remote
> access (for example, pull and clone). Output is, as already reported
> multiple times on this list:

> remote: Counting objects: 19973, done.
> remote: Compressing objects: 100% (7588/7588), done.
> fatal: read error on input: Bad address.99 KiB | 103 KiB/s

This occurs when cloning via the git: protocol.  Can you instead clone
with the http: protocol to work around it?  I still haven't had time to
try and figure out why this fails for some repositories, but not others.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkohK/wACgkQ84KuGfSFAYDMYACeOJjOlgBNvUwPpu2hYT+1hwSO
6CIAn3ykMEJlkiAK4YPoZji2DncjSdLi
=8/fT
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

