1.0 approaches

[Martin Geisler]

Stephen Touset <stephen at touset.org> writes:

> On Feb 8, 2008, at 10:14 AM, Marcin Kasperski wrote:
>
>> The confusion is fairly frequent. And the change need not be
>> invasive, old convention may be still handled....
>
> This would cause even more confusion, given that no other URI on the
> planet uses it. Again, the old way isn't a "convention". It's a
> documented standard.

And this standard conflicts with the standard use of SSH -- when using a
program like Mercurial that runs some data over a SSH connection, then
it would be nice if the program followed the standard syntax for SSH
paths (like rsync does, for example). I expected Hg to behave like that
too in the beginning.

When cloning a repository on the local file system one can specify the
path using, well, a path and not a URI (thanks for that, I don't really
like those file:///foo/bar URLs). So the argument is not that Mercurial
always uses a URI here.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20080208/7364b850/attachment.pgp