On Wed, Apr 13 2022, Tao Klerks via GitGitGadget wrote: > Under python2, git-p4 "naively" writes the Perforce bytestream into git > metadata (and does not set an "encoding" header on the commits); this > means that any non-utf-8 byte sequences end up creating invalidly-encoded > commit metadata in git. If it doesn't have an "encoding" header isn't any sequence of bytes OK with git, so how does it create invalid metadata in git? Do you mean that something on the Python side gets confused and doesn't correctly encode it in that case, or that it's e.g. valid UTF-8 but we're lacking the metadata?
