Re: [boost] [conversion] Isolating the phantom file changes problem
In addition to re-normalizing the line endings, we could also start enforcing coding standards, e.g. tabs converted to spaces standard via gitconfig/gitattribute filters. Git allows you to define filters in your .git/config or ~/.gitconfig file and specifying their use in .gitattributes, e.g. in .gitconfig: # Convert tabs to 4 spaces (uses Linux expand/unexpand commands, so not cross-platform) [filter "tabspace"] smudge = unexpand --tabs=4 --first-only clean = expand --tabs=4 --initial Then in .gitattributes: # Code formats *.c text filter=tabspace *.cpp text filter=tabspace *.h text filter=tabspace *.hpp text filter=tabspace *.ipp text filter=tabspace *.tpp text filter=tabspace On a related topic, what is the svneol .gitattribute being used in the .gitattributes file do? I couldn't find it documented (I discovered the filter attribute while searching for the svneol attribute). Also, the mime type specified in a # comment following some attribute rule specification doesn't seem to be a supported syntax, i.e. the '#' has to be in the first column. Michael On Wed, Nov 27, 2013 at 3:02 PM, Gavin Lambert <gavinl@compacsort.com>wrote:
On 28 November 2013 08:49, Cox, Michael <mhcox@bluezoosoftware.com> wrote:
...automatically behind the scene? Scary! IMHO, this belongs to commit hooks. Qt's sanitize-commit may be a good example https://qt.gitorious.org/qt/qtrepotools/source/b69da7d675774be14027808328eaf... Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
On Thu, Nov 28, 2013 at 5:00 AM, Mateusz Loskot <mateusz@loskot.net> wrote:
Michael and Mateusz, Yes - sanitizing and commit hooks are important topics. But the way to handle them is to start a new thread so that they don't get lost in the line-ending bicycle shed discussion. Thanks, --Beman
participants (3)
-
Beman Dawes -
Cox, Michael -
Mateusz Loskot