On Tue, Jul 11, 2017 at 10:20:43AM +0200, Torsten Bögershausen wrote: > > No problem. I actually think it would be interesting if Git could > > somehow detect and warn about this situation. But the obvious way to do > > that would be to re-run the clean filter directly after checkout. And > > doing that all the time is expensive. > > Would it be possible to limit the round-trip-check to "git reset --hard" ? > If yes, possibly many users are willing to pay the price, if Git tells > the "your filters don't round-trip". (Including CRLF conversions) Anything's possible, I suppose. But I don't think I'd want that feature turned on myself. > > Perhaps some kind of "lint" program would be interesting to warn of > > possible misconfigurations. Of course people would have to run it for it > > to be useful. :) > > What do you have in mind here ? > Don't we need to run some content through the filter(s)? I was thinking of a tool that could run a series of checks on the repository and nag about potential problems. One of them could be doing a round-trip repo->clean->smudge for each file. Another one might be warning about files that differ only in case. The idea being that users could run "git lint" if they suspect something funny is going on. I dunno. It may be a dead-end. Most such oddities are better detected and handled during actual git operations if we can. So this would really just be for things that are too expensive to detect in normal operations. -Peff
