Re: [PATCH 5/5] builtin-remote: Make "remote -v" display push urls
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:46:56
Michael J Gruber [off-list ref] writes:
Junio C Hamano venit, vidit, dixit 09.06.2009 18:25:quoted
Michael J Gruber [off-list ref] writes:quoted
Example with "mjg" having 1 url and 1 pushurl, "origin" having 3 urls, sb having 1 url: mjg git://repo.or.cz/git/mjg.git (fetch) mjg repoor:/srv/git/git/mjg.git (push) origin git://repo.or.cz/git.git (fetch) origin git://repo.or.cz/git.git (push) origin git://git2.kernel.org/pub/scm/git/git.git (push) origin git://repo.or.cz/alt-git.git (push) sb git://repo.or.cz/git/sbeyer.git (fetch) sb git://repo.or.cz/git/sbeyer.git (push)The readers will get distracted, saying "eh, git:// can be used for push?" (and the answer is "yes, sometimes, but not for repo.or.cz") even though that is not the point of these illustrations. For these examles, I think it is better to use "repo.or.cz:foo.git" style, instead of "git://".Uhm, isn't host:foo.git equivalent to ssh://host/foo.git?
The primary point is git:// is usually considered read-only and not for push. I personally am more used to host:repo and that is why I wrote it that way; besides, the second line in your example already uses that notation, not the ssh:// one.