9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: lucio.dere@gmail.com, ori@eigenstate.org
Cc: 9fans@9fans.net
Subject: Re: [9fans] Getting git9 -- moved to github.
Date: Sun, 2 Feb 2020 20:11:51 -0800	[thread overview]
Message-ID: <00BF6A37730ADB3A0B18AEEBC1377ADF@eigenstate.org> (raw)
In-Reply-To: <CAJQ9t7j+enip5B0_OhROCzw=wLTKqc29xaDcnBDVgQDGg--HkA@mail.gmail.com>

> Looking at 9legacy's ssh/(ssh1 ssh2) may say otherwise and that I'm
> willing to concede. But a "-p 4321" option and its equivalent seems to
> me to require just a couple of additional lines in the ssh(1) man page
> to be worth accepting.

Do you intend to make this syntax work consistently across all of plan 9?

> 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


  reply	other threads:[~2020-02-03  4:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 17:03 ori
2020-01-27 21:23 ` [9fans] " Sergey Zhilkin
2020-02-02  9:58 ` Lucio De Re
2020-02-02 10:35   ` kvik
2020-02-02 14:39     ` Lucio De Re
2020-02-02 22:47       ` hiro
2020-02-02 23:28         ` cinap_lenrek
2020-02-03  0:55   ` ori
2020-02-03  0:57   ` ori
2020-02-03  4:07     ` Lucio De Re
2020-02-03  4:11       ` ori [this message]
2020-02-03  7:39         ` Lucio De Re
2020-02-03 10:01           ` hiro
2020-02-03 11:10             ` Lucio De Re
2020-02-03 13:54               ` hiro
2020-02-03 14:40                 ` Lucio De Re
2020-02-03 16:14                   ` ori
2020-02-04  4:07                     ` Lucio De Re
2020-06-20 15:58                       ` Lucio De Re
2020-02-03 20:42                   ` cinap_lenrek
2020-02-04  4:03                     ` Lucio De Re

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00BF6A37730ADB3A0B18AEEBC1377ADF@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9fans@9fans.net \
    --cc=lucio.dere@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).