"Alex Riesen" [off-list ref] writes:
On 4/23/07, Junio C Hamano [off-list ref] wrote:
quoted
* jc/attr (Sat Apr 21 03:14:13 2007 -0700) 2 commits
- Add 'filter' attribute and external filter driver definition.
- Add 'ident' conversion.
As 'ident' conversion is stateless, I do not mind too much
including it in v1.5.2-rc1. On the other hand, the arbitrary
'filter' is quite contentious, although the character-code
conversion example I gave myself might be a good enough reason
for people to want it. Undecided.
Can I suggest a config option to completely disable content
munging code? So that people who really care about the
real content, or just don't have the tools for the filters still
can checkout the repos depending on the filters.
The code may have bugs, but the intent is that you can have this
line in your $GIT_DIR/info/attributes to override whatever
attribute settings used in .gitattributes files that are
in-tree:
* !ident !filter
Junio C Hamano, Mon, Apr 23, 2007 19:15:16 +0200:
quoted
quoted
As 'ident' conversion is stateless, I do not mind too much
including it in v1.5.2-rc1. On the other hand, the arbitrary
'filter' is quite contentious, although the character-code
conversion example I gave myself might be a good enough reason
for people to want it. Undecided.
Can I suggest a config option to completely disable content
munging code? So that people who really care about the
real content, or just don't have the tools for the filters still
can checkout the repos depending on the filters.
The code may have bugs, but the intent is that you can have this
line in your $GIT_DIR/info/attributes to override whatever
attribute settings used in .gitattributes files that are
in-tree:
* !ident !filter
Imagine a project which started using the attributes at some point of
time. And imagine developers whose repos suddenly start breaking
because of clueless integrator created a filter which does not work
anywere but his system (typical, really) and didn't tell anyone to
update their configuration (whereas .gitattribute files are in working
trees already).
How do you suggest to distribute filter configurations, BTW?
They are not cloned (can they?)
How about checkout performance impact? (in case they are not active,
of course. You're hosed anyway if the filters used. Especially if you
happen to have real big files).