Re: Encoding of repository hook parameters

[Philip Martin]
> The first argument to all the repository hooks is the path to the
> repository and the value has been converted from UTF-8 to the native
> encoding of the process that invoked the hook.

Wait, why are you treating a filename on the host system as anything
other than an opaque string of bytes? I understand the path *within* a
repository is charset-converted in checkouts, so that's a different
matter, but the physical filesystem path *to* a repository is useful in
no other form than its original encoding, which may or may not have
anything to do with utf-8.

Pardon me if I'm missing something obvious, but I see no point in ever
converting that path to or from anything. (Well, in URLs it needs
URL-encoding obviously, but we aren't talking about those.)