From mboxrd@z Thu Jan 1 00:00:00 1970 From: david@lang.hm Subject: Re: .gittattributes handling has deficiencies Date: Sun, 21 Oct 2007 10:57:18 -0700 (PDT) Message-ID: References: <1192956535617-git-send-email-prohaska@zib.de> <1A07FEE6-88D8-4ED7-BEFD-F7F3B71310A5@zib.de> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: git@vger.kernel.org To: Steffen Prohaska X-From: git-owner@vger.kernel.org Sun Oct 21 19:52:25 2007 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1IjeyM-00038r-VG for gcvg-git-2@gmane.org; Sun, 21 Oct 2007 19:52:23 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751828AbXJURvr (ORCPT ); Sun, 21 Oct 2007 13:51:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751815AbXJURvq (ORCPT ); Sun, 21 Oct 2007 13:51:46 -0400 Received: from dsl081-033-126.lax1.dsl.speakeasy.net ([64.81.33.126]:57388 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751330AbXJURvo (ORCPT ); Sun, 21 Oct 2007 13:51:44 -0400 Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id l9LHphtc032568; Sun, 21 Oct 2007 10:51:43 -0700 X-X-Sender: dlang@asgard In-Reply-To: <1A07FEE6-88D8-4ED7-BEFD-F7F3B71310A5@zib.de> Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: On Sun, 21 Oct 2007, Steffen Prohaska wrote: > On Oct 21, 2007, at 7:09 PM, david@lang.hm wrote: > >> On Sun, 21 Oct 2007, Steffen Prohaska wrote: >> >>> On Oct 21, 2007, at 11:19 AM, david@lang.hm wrote: >>> >>>>> But this is really hard to solve. We would need to compare >>>>> attributes before and after for _all_ files that have attributes >>>>> in one of the two commits and check if they changed. If so, we >>>>> need to do a fresh checkout according to the new attributes. >>>> if you know that you will get the new .gitattributes if it changes, setup >>>> a post-checkout hook to checkout everything if it has changed. it's far >>>> from ideal, but it should be a good, safe, first approximation. >>> >>> >>> That's not good enough. I'll stop using .gitattributes. I >>> need to teach >40 devs how to use git on Windows. I only use >>> features that work flawlessly. .gitattributes doesn't. It bit >>> me twice now. >> >> why would checking everything out if .gitattributes has changed not work? I >> can see why _not_ doing so would cause problems, and I freely acknowledge >> that this approach imposes a performance hit by checking everything out >> twice, but I don't see how it would not be reliable. > > What do you mean by "checking out everything"? > Which command do you propose? something like git checkout -f David Lang