Re: [PATCH v2] post-receive-email: explicitly set Content-Type header
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Oct 7, 2011, 20:19 UTC
- Message-ID
- <20111007201932.GC29712@elie.hsd1.il.comcast.net>
- In-Reply-To
- <20111007165209.595834f2@ashu.dyn.rarus.ru>
Alexey Shumkin wrote:
Show 5 quoted lines
> In development process under Windows non-UTF-8 > encoding is used (cp1251 in my case). So, filenames have this encoding, > and as we know Git stores their names as is - in cp1251 - without a > conversion. And filenames are also used in diff-stat (with > core.quotepath= false
Yes, when a person sets [core] quotepath to false, I think it's fair to assume for now that the filenames are in the same encoding as everything else (whether that's UTF-8 or something else). Maybe it would be possible in a separate patch to add a configurable list of encodings to try out when formatting paths for display.
Jonathan