clone with ssh doesn't work

[Eric Hopper]

On Mon, Nov 07, 2005 at 06:35:41PM +0100, e8nwt4002 at sneakemail.com wrote:
> As far as I know GNOME VFS follows but extends the RFC URI
> specification (RFC 2396). It does not provide user-directory relative
> path specification. The options I see are:

Looking at the RFC, it clearly specifies a way to talk about directories
both relative to the user's home directory and relative to the 'root'
directory of the system.  And the way it specifies is exactly how
Mercurial does it, and not how GNOME VFS works.

> 2. Use whatever the SSH team thought were best for specifying paths and
> be compliant with them. Users of SSH will feel home instantly.

Their method looks more like NFS mount specifications than a URL.

> I personally would choose 2 because one can assume the SSH team knows
> about the RFC and did what it seemed best.

Mercurial already does what the RFC says.  It's one of the few software
programs that does it the right way.  Since all of the other software
programs I've seen attempt this either don't use URL syntax at all
(ssh), or don't have a way to talk about both a directory relative to a
user's home directory, and a directory relative the system root, I'd say
the RFC is a better standard than any implemented by current programs
that do not follow the RFC.

Have fun (if at all possible),
-- 
"It does me no injury for my neighbor to say there are twenty gods or no God.
It neither picks my pocket nor breaks my leg."  --- Thomas Jefferson
"Go to Heaven for the climate, Hell for the company."  -- Mark Twain
-- Eric Hopper (hopper at omnifarious.org  http://www.omnifarious.org/~hopper) --
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20051107/62b967a0/attachment-0001.asc>