X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-4.0 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: Eric Blake <ebb9@byu.net>
Subject:  Re: git: need 1.6.2 for cygwin
Date: Mon, 6 Apr 2009 20:09:13 +0000 (UTC)
Lines: 32
Message-ID:  <loom.20090406T195745-454@post.gmane.org>
References:  <3ae83b000904061141udf4991mb53fdac5095cdc6f@mail.gmail.com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
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

John Bito <jwbito <at> gmail.com> writes:

> I encountered a problem that caused my GitHub repository to be
> unusable after a push.  The GitHub folks indicated that my use of git
> 1.6.1 together with JGit 0.4 may have caused the problem.  I could use
> msysgit 1.6.2.1, but I like Cygwin and would prefer to continue with
> that. Could you please let me know if git 1.6.2 for Cygwin might be
> available in the next week or so?

I make no promises on my time schedule, but yes, I would also like to release 
git 1.6.2.2 soon.  But there are still reports on this list of a reproducible 
crash that I am still trying to understand, even though it doesn't impact my 
personal usage of git.  Meanwhile, remember that this is a volunteer effort.  
Among things competing for my free time are completing updated cygwin packages 
for coreutils 7.2, findutils 4.5.4, and bash 4.0; keeping up with upstream 
maintenance on m4 and autoconf.  And don't forget to throw $DAYJOB into the 
mix.  Just to give you a realistic picture of how unpredictable my free time 
can be, my original goal was to release m4 1.4.13 in January, but I did not get 
to it until April 1st; on the other hand, I recently had a lot of free time, as 
evidenced by the upstream releases of both autoconf 2.63b and m4 1.4.13 in less 
than one week, along with a flurry of several of my cygwin packages.

In the meantime, you can compile the latest git from sources yourself on cygwin 
(I do that myself; I'm comfortable using a self-built git that meets my needs, 
even when I don't know why it is crashing for others on the list).  And by 
building your own copy, you end up neither waiting for me, nor using msysgit.

-- 
Eric Blake
volunteer cygwin git maintainer




--
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/