X-Spam-Check-By: sourceware.org
From: Jari Aalto <jari DOT aalto AT cante DOT net>
To: Eric Blake <ebb9 AT byu DOT net>
Subject: Re: [BUG] Git v1.5.0.3: fatal: Unable to write new index file
CC: <virgo977virgo AT gmail DOT com>, cygwin AT cygwin DOT com
Date: Sun, 05 Aug 2007 00:51:29 +0300
Message-ID: <k5sbezoe.fsf@blue.sea.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Antivirus: VAMS
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


    No need to cc me; I read the list.

    According to Stefano Spinucci on 3/17/2007 7:24 AM:
    > Then, I hope the cygwin Git binary 'll be compiled with NO_MMAP;
    > otherwise, needing to work on a FAT32 fs, I'll have to recompile Git
    > manually.

    http://cygwin.com/ml/cygwin-announce/2007-03/msg00005.html

    "However, it means that this version does assume that you are not using
    FAT or FAT32 to hold your repositories, since they do not store file
    permissions very accurately."

    I highly recommend that you upgrade to NTFS.  FAT32 is not secure.  If you
    insist on using FAT, then you are correct - you must recompile git yourself.

Thsi is not an option. Many people use FAT32 due to better
interoprability dusing multi-boot environments. Please distribute git
wit FAT32 support enabled. Windows workstations are *one* user
workstations, so the point of being "secure" is less important than
interoperability.

Jari



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