X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Eric Blake <ebb9 AT byu DOT net>
Subject:  Re: Upgrade to git 1.5.3 broke git-commit
Date: Thu, 20 Sep 2007 18:08:17 +0000 (UTC)
Lines: 28
Message-ID:  <loom.20070920T200146-333@post.gmane.org>
References:  <loom DOT 20070920T174621-935 AT post DOT gmane DOT org>
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 AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

chris ortman <chrisortman <at> gmail.com> writes:

> 
> I just upgraded my cygwin git package to 1.5.3 and how when I try to commit 
and
> allow git to launch vim to enter a commit message i have problems.
> 
> The commit message normally has some content already in it, but it is now 
blank
> and won't let me save because it says the file can not be opened for writing.

IWJFFM.  It sounds like you may have a stale file, or awkward permissions which 
are getting in the way, when vi tries to open and/or overwrite 
the .git/COMMIT_EDITMSG file.

Also, are you using 1.5.24 or a CVS snapshot?  There was a window of CVS 
snapshots that failed to create files on certain filesystems, but that appears 
to be fixed now.  Also, with the latest CVS snapshot, there are still problems 
with pipe behavior that can interfere with gitk and git-gui.

One other thing: git 1.5.3.2 was announced today, and I'll probably be building 
a new package soon.  So it would be nice to ensure that I don't need some sort 
of cygwin-local patch to work around your issue, since I can't reproduce it.

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