RFC: safe pattern matching for problematic encoding

Martin Geisler martin at geisler.net
Wed May 23 15:50:53 CDT 2012


Matt Mackall <mpm at selenic.com> writes:

> On Wed, 2012-05-23 at 15:14 +0200, Antoine Pitrou wrote:
>> On Wed, 23 May 2012 14:53:43 +0200
>> Mads <mads at kiilerich.com> wrote:
>> > 
>> > > As you noticed, wrapping/hooking points are scattered in widely, so I
>> > > think that this implementation is not so good. But I don't have any
>> > > other ideas.
>> > >
>> > > Are there any other ideas to solve this problem ?
>> > 
>> > The only viable solution is to consistently use utf-8 inside Mercurial.
>> 
>> Or to consistently use unicode strings ;)
>
> <rage class=python3>
> Yes, please go waste the next year or two of your life working on that
> brilliant idea. Don't come back until you can preserve mixed filename
> encodings on Linux while interoperating with old hg clients. Best of
> luck.
> </rage>

Is mixed filename encodings really something we want to support?

It sounds like a super rare situation to me, and a situation that the
users would be happy to correct if it is detected.

Some users would probably say "why did you even allow me to make this
mess in the first place?!" and consider it a bug that such repositories
can exist today.

-- 
Martin Geisler

aragost Trifork
Commercial Mercurial support
http://aragost.com/mercurial/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120523/14615399/attachment.pgp>


More information about the Mercurial-devel mailing list