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.
some of the things that .gitattributes is being talked being used for about for
are local, some are per-repo
per the prior discussion of how many places to check a local configuration
should override the per-repo setting.
David Lang
Of course, the config language may not be wonderful for this. But we could
certainly have something like
[format "crlf"]
enable = true
text = *.[ch]
binary = *.jpg
which would just override the built-in rules (where anything that doesn't
match is just "auto-content"). And make the default built-in ones be good
enough that in _practice_ you never even need this in the first place.
Linus
-
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
-
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