Re: Git on Windows, CRLF issues
- From
Avery Pennarun <apenwarr@gmail.com>
- Date
- Apr 23, 2008, 23:04 UTC
- Message-ID
- <32541b130804231604r4c439fa5va5c01bfd53a22cc7@mail.gmail.com>
- In-Reply-To
- <7vprsgqiq1.fsf@gitster.siamese.dyndns.org>
On 4/23/08, Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
> But once you start saying "even originally the same blob (i.e. identified > by one object name) can be rewritten into different result, depending on > where in the tree it appears", would it make sense to have blob filters to > begin with? > > Shouldn't that kind of of context sensitive (in the space dimension -- you > can introduce the context sensitivity in the time dimension by saying > there may even be cases where you would want to filter differently > depending on the path and which commit the blob appears, which is even > worse) filtering be best left to the tree or index filter?
What I really want is the equivalent of "dos2unix --recursive *.c *.txt etc" for all commits.
Theoretically, a .txt file might be renamed to a .jpg file, in which case funny things would happen with such a filter, depending which commit was seen first.
I'm pretty confident that this will never happen to me, but it's a valid concern.
Have fun,
Avery