[PATCH 1 of 1] handle file URIs correctly, according to RFC 2396 (issue1153)

[Martin Geisler]

Sune Foldager <cryo at cyanite.org> writes:

> Matt Mackall wrote:
>> On Tue, 2009-12-01 at 13:54 +0100, Sune Foldager wrote:
>>> The new code aims to implement the RFC correctly for file URIs.
>>> Previously they were handled incorrectly in several ways, which
>>> could cause problem on Windows in particular.
>> 
>> Let's put this in stable after today's 1.4.1.
>
> Alright, sounds good. Before doing so, I still need some help with
> running all the convert tests, to make sure we don't break anything.

No failures here! I had some skipped tests:

Skipped test-convert-tla: missing feature: GNU Arch tla client
Skipped test-casefolding: missing feature: case insensitive file system
Skipped test-convert-mtn: missing feature: monotone client (> 0.31)
Skipped test-convert-baz: missing feature: GNU Arch baz client
Skipped test-convert-p4-filetypes: missing feature: Perforce server and client
Skipped test-convert-p4: missing feature: Perforce server and client
Skipped test-no-symlinks: system supports symbolic links

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20091201/6ab306b8/attachment.pgp>