[PATCH stable v2] convert: use original local encoding when converting from Perforce
mpm at selenic.com
Wed Jul 22 12:15:56 CDT 2015
On Wed, 2015-07-22 at 16:59 +0100, Eugene Baranov wrote:
> # HG changeset patch
> # User Eugene Baranov <eug.baranov at gmail.com>
> # Date 1437580631 -3600
> # Wed Jul 22 16:57:11 2015 +0100
> # Node ID 67e43f16613874f2c5782ddf11e6f3ee17f1b586
> # Parent bcb96f98d9cfade5098a9a12b49714d218441f83
> convert: use original local encoding when converting from Perforce
Since encoding is tricky, I'd like to see a little more rationale here.
Please take a look at:
..and tell us briefly what p4's strategy is and why this is a good fit.
Or add a comment.
Also, Frank presumably had a reason for using Latin1 in the first place.
My guess is that he has a utf-8 locale and thus this would break his
setup, which isn't great. So whether something like this can go into
stable isn't clear.
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial-devel