Avery Pennarun schrieb: > On 4/23/08, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote: >> 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 -- 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
