Re: [9fans] Getting git9 -- moved to github.

[Lucio De Re <lucio.dere@gmail.com>]

On 2/3/20, ori@eigenstate.org <ori@eigenstate.org> wrote:
>
> Do you intend to make this syntax work consistently across all of plan 9?
>
Only 9front SSH, because it begs to be available. Legacy SSH is
different (or I'm missing a big chunk of patching and I'll never
really get there, I don't think).

>> As for git9/proto.c, I merely re-arranged the code, mostly. Something
>> about a trailing colon was in place, but I did not entirely understand
>> what it attempted to take care of
>
> This is a valid repository syntax:
>
> 	git+ssh://user@host.com:path/to/repository
>
Git can be obscure: the leading / in the "path" shouldn't be optional. Yet

	git+ssh://user@host.com:port/path/to/repository

is also valid (or at minimum, works) with "/path" treated as local to
the user's $HOME (ssh landing directory). Or am I getting that wrong?

But Unix "scp" has a similar "flaw", except you are compelled to use
the -P (note the case inconsistency) option to provide a non-standard
port, so the leading slash would then pin the "/path" to "/". I guess
I need to brush up on the standards around URLs?

-- 
Lucio De Re
2 Piet Retief St
Kestell (Eastern Free State)
9860 South Africa

Ph.: +27 71 471 3694
Cell: +27 83 251 5824