From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Strapetz Subject: Re: Applying .gitattributes text/eol changes Date: Tue, 11 Jan 2011 10:29:02 +0100 Message-ID: <4D2C22DE.2040804@syntevo.com> References: <4D220500.2000104@syntevo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Tue Jan 11 10:29:35 2011 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 1PcaXm-0004fE-IR for gcvg-git-2@lo.gmane.org; Tue, 11 Jan 2011 10:29:34 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755523Ab1AKJ3M (ORCPT ); Tue, 11 Jan 2011 04:29:12 -0500 Received: from syntevo.com ([85.214.39.145]:39964 "EHLO syntevo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752971Ab1AKJ3H (ORCPT ); Tue, 11 Jan 2011 04:29:07 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) with ESMTPSA id 94BD8174006 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 In-Reply-To: <4D220500.2000104@syntevo.com> X-Enigmail-Version: 1.1.1 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Any ideas on this? Thanks, Marc. On 03.01.2011 18:18, Marc Strapetz wrote: > I'm looking for an unobtrusive way to apply (committed) changes for > text/eol attributes to the working tree. For instance, after having > changed "*.txt eol=crlf" to "*.txt eol=lf", all *.txt files should be > converted from CRLF to LF endings. The only advice I found so far is to > remove .git/index and do a reset --hard. The disadvantage of this > approach is that every file will be touched: > > - although the content does not change, timestamps will be changed. This > makes tools like IDEs assume that the file content has been changed. > (Even if the timestamps would be properly reset, the replacement of the > files would have triggered system file change notifications and I'd > expect various tools to still reload these files) > > - there will be warnings for files which are locked by other processes > (at least on Windows). I'm usually seeing this for JAR files which are > not affected by eol-attribute changes at all. > > One solution I could think of which might be helpful in other situations > as well would be to have an "--unobtrusive" option for reset which would > only replace a file if the content has actually been changed. > > Marc. > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > >