From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joshua Jensen Subject: Re: What's cooking in git.git (Dec 2010, #06; Tue, 21) Date: Fri, 24 Dec 2010 13:02:12 -0700 Message-ID: <4D14FC44.5070309@workspacewhiz.com> References: <7vlj3i5zz9.fsf@alter.siamese.dyndns.org> <7vfwto2ytb.fsf@alter.siamese.dyndns.org> <4D13DCDD.3050300@workspacewhiz.com> <7vzkrvynz5.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nguyen Thai Ngoc Duy , git@vger.kernel.org To: Junio C Hamano X-From: git-owner@vger.kernel.org Fri Dec 24 21:03:14 2010 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PWDr8-0007g3-Ds for gcvg-git-2@lo.gmane.org; Fri, 24 Dec 2010 21:03:14 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753125Ab0LXUCP (ORCPT ); Fri, 24 Dec 2010 15:02:15 -0500 Received: from hsmail.qwknetllc.com ([208.71.137.138]:34502 "EHLO hsmail.qwknetllc.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752830Ab0LXUCO (ORCPT ); Fri, 24 Dec 2010 15:02:14 -0500 Received: (qmail 4398 invoked by uid 399); 24 Dec 2010 13:02:13 -0700 Received: from unknown (HELO ?192.168.1.100?) (jjensen@workspacewhiz.com@76.27.116.215) by hsmail.qwknetllc.com with ESMTPAM; 24 Dec 2010 13:02:13 -0700 X-Originating-IP: 76.27.116.215 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b3pre Thunderbird/3.1.7 In-Reply-To: <7vzkrvynz5.fsf@alter.siamese.dyndns.org> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: ----- Original Message ----- From: Junio C Hamano Date: 12/24/2010 12:23 PM > Joshua Jensen writes: > >> Having said that, I have had 100 people using the jj/icase-directory >> series on Windows daily for 4 months now without issue. Prior to >> that, a majority of the series had been used for a full year by a >> dozen people.... > Just to make sure nobody misunderstood me, what I was proposing to put on > hold was not the "case insensitivity" work of yours, which is already > scheduled to be part of the coming release. Ah. I completely misinterpreted your statement. Well, that's exciting. After it goes live, I'll have some more case insensitivity patches forthcoming for discussion. -Josh