Thread (25 messages) flat view 25 messages, 7 authors, 2016-06-15

Re: Git on Windows, CRLF issues

From: Johannes Sixt <hidden>
Date: 2016-06-15 22:44:31

Avery Pennarun schrieb:
On 4/23/08, Johannes Sixt [off-list ref] wrote:
quoted
In practice, this is not sufficient. The blob filter must have an
 opportunity to decide what it wants to do, not just blindly munge every
 blob. The minimum is a path name, e.g. in $1:
Actually, it may not have been intentional, but because of the way
'eval' works, the munge script will find that $path already contains
the path of the file being munged.  Works for me.
Yes, of course! So I stand corrected, and Jeff's patch makes sense.

For consistency's sake, the path should be made available in, say,
GIT_BLOB_PATH just like the commit is available in GIT_COMMIT.

-- Hannes
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help