[MERGE] support for win32 UNC path (bug #57869)

[Alexander Belchenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Arbash Meinel пишет:
> Alexander Belchenko wrote:
>> This patch provide support for win32 UNC path like: \\HOST\path.
>> Here the test and modification in urlutils win32*/to/from/_url.
>>
>> bzr branch http://bialix.aaronbentley.com/win32.unc-path/
>>
> 
> It makes more sense from the URL spec that these would be interpreted as:
> 
> file://host/path
> 
> rather than
> file://///host/path
> 
> In general URL's are:
> 
> <identifier>://<host>/path
> 
> And 'file:///' has 3 slashes because you have no host.
> 
> So if you are switching to a form that has a host: 'file://host/' makes
> sense.

Well, I'm not expert in file URLs, but I try to be consistent with
browsers installed on my machine. file:///// -- it's the single form of
URL that understand Firefox. IE behaves more smart and accept almost any
quantity of slashes -- 2, 4, 5, 6, -- but not 3, because as you said 3
slashes maps to local filesystem (with no root).

I'm personally think that we can do what we want in this case because
file URLs is needed only for bzr internals and *never* should be faced
to user because they useless for other programs (non-browsers).

Actually, I don't think that Firefox should be standard for us, because
it does not accept plain UNC path in their navigation pane.

I just want to teach bzr works with UNC path, because I need this
feature, and I don't care about internal representation (2 vs 5
slashes). I'll rework my patch.

Also I have a question about entry in NEWS file: do I need to move my
entry to BUG FIXES section?

> 
> That said, I can see why it might be easier to do it the other way.
> 
> So I would like to request that you do it the other way, but if you feel
> it would be too difficult, I can approve this form.

Alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFd8+zzYr338mxwCURAs4VAJ9pxmCK7MNxZ461cTSwEDYyuYnlAwCfb7yC
4HtTAAP+x72bfQJi0qL42A8=
=5qUo
-----END PGP SIGNATURE-----