I have a particular commit that has a path that becomes quoted and escaped due to having the byte \x80 in it as a filepath, eg the diff has:
`a/foo/bar-\200-baz` (I am not using -Z), git diffing the commit emits the path no problem. however I've having issues trying to git blame on the parent commit. I basically want to turn around and use 'foo/bar-\200-baz' as an input for the path to git blame. Here is what I have tried: `git blame <sha> -- 'foo/bar-\200-baz' ` - doesnt work, says path doesnt exist `git blame <sha> -- foo/bar-�-baz` (thats the literal value in shell) , same thing, path doesnt exist however on *nix shells where I can evaluate the escape, things work, for example: $ git blame <sha> -- `printf 'foo/bar-\200-baz' ... works .. What I'm ultimately after is a way to take the C escaped output string and use it directly as an input for other git commands (this is complicated further by certain runtimes always trying to encode arguments to processes..) Is there already a flag or option way to do this? If not I'd be willing to create a patch for this functionality so its balanced, if well received. Thanks, Dexter -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
