Phillip Wood, Apr 03, 2023 at 16:09: > Usually git commands that produce or consume paths either use quoted > paths terminated by LF or unquoted paths terminated by NUL. That way > there is no ambiguity when a path contains LF. Thinking again about that. The probability that a file path name generated by git-format-patch would contain LF is close to zero. However, reading per line is more natural and more in line with other hooks that read from stdin. Having that single hook separating stuff in stdin with NUL bytes is weird from a user point of view. Don't you think it would be an acceptable limitation?
