X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=lt6CJJt+DhAM3uUJRyKquM4gLx1XO2uu94ghGqrr0Yc
	Bf72sQ+vpbSak0r9DvKkwdVUMlQfHVq0lmdkcBhKpNcHVd+BcOlHGxqCpMXqPISt
	D8EYcxno7D0Tm5zS5Z61HepFzaM9PIL2Zhl4yQPa8T1VY3lw1Mf0uuJzNwrDcUuU
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=/sXfsuzry2g8vp+RYYm6G9+gLrg=; b=R7nU8h2G6/yrxM0qY
	1EloPp405G9uYpjdOjbWWxIA0jtOnAne7DxV/xemyw6NlY6qhaln1psf5jQvwrwd
	2R1PF62L2UrnH/TcAo/rbnOy3zcOtKs0btigGa/HawwH3gC7W4RZ8e/Uzlz978S5
	lbVe08iIxqLWnVRiFtXV2H629U=
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
X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_20,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2
Message-ID: <520E2773.4060403@cwilson.fastmail.fm>
Date: Fri, 16 Aug 2013 09:21:55 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject: Re: Lack of case-sensitive filename handling with git 1.7.9-1 for Cygwin 64-bit
References: <CAGZiy71u1Ci_2Uw6jgAw3-9gCgwVrS1ae2Bpz9HCbnj2+EZexA AT mail DOT gmail DOT com> <20130816081743 DOT GC2562 AT calimero DOT vinschen DOT de>
In-Reply-To: <20130816081743.GC2562@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 8/16/2013 4:17 AM, Corinna Vinschen wrote:
> I assume the format of the git database files depends on the
> architecture.  Therefore it's probably not advisable to use
> a git repo created under 32 bit git with a 64 b

Oh, wow. That's...awkward. I'm sharing the same drive area mounted in 
both cyg32 and cyg64 for my builds, and repo'ing the cygport & related 
files using git.  So far I always have done the git manipulations in 
cyg32...guess I need to make sure I continue to do it that way!

(I could always "clone" the repo(s) to a new area on cyg64, but I would 
probably have to use one of the wire protocols and not the file system 
protocol to do it).

--
Chuck



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