Hi, On Tue, 20 Feb 2007, Linus Torvalds wrote: > On Wed, 21 Feb 2007, Johannes Schindelin wrote: > > > > Um, I don't want to spoil the party, but was not the original idea of this > > auto-CRLF thing some sort of "emulation" of the CVS text checkout > > behaviour? > > > > In that case, .gitattributes (I mean a tracked one) would be wrong, wrong, > > wrong. > > > > It's a local setup if you want auto-CRLF or not. So, why not just make it > > a local setting (if in config or $GIT_DIR/info/gitattributes, I don't > > care) which shell patterns are to be transformed on input and/or output? > > That is a good point. We *could* just make it a ".git/config" issue, > which has the nice benefit that you can just set up some user-wide rules > rather than making it be per-repo. Yes, that's a nice side effect. > Of course, the config language may not be wonderful for this. Like you wrote in your example, most shell patterns are no problem in the config. > And make the default built-in ones be good enough that in _practice_ you > never even need this in the first place. This is really, really important. We already see many users using git, expecting it somehow to figure out what they want without them having read TFM. Anyhow, I am right now talking with Junio (on IRC; my 2nd day wasting time in chatspace ;-), among other things about the import/export filters. We should at least keep in mind that this would be nice to have, and leave a door open for them when we do this stuff. Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html