On Wed, Apr 23, 2008 at 12:58:57PM +0200, Johannes Sixt 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:
>
> new=$(git cat-file blob $sha1 |
> $SHELL_PATH -c "$filter_blob" ignored "$path" |
> git hash-object -w --stdin)
I intentionally left that out, because:
- I assumed if you were going to do trickery with pathnames, you
should just be doing an index filter
- it violates the cache assumption, which is that blob $X is always
transformed the same way
I assume you are wanting to do something like:
git filter-branch --blob-filter '
case "$1" in
*.jpg) cat ;;
*) tr a-z A-Z ;;
esac
'
Obviously it is unlikely to get the same blob sha1 as "foo.jpg" and
"foo.txt", but it just feels a little wrong.
-Peff
--
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
