Re: [PATCH 5/5] builtin-remote: Make "remote -v" display push urls

Junio C Hamano venit, vidit, dixit 09.06.2009 18:25:

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?

In any case, if you clone from a fetch-only url (which is the typical
head start) then the default push url does not work (like sb above),
before as well as after this series.

I noticed that I left an URL alias ("repoor" = "repoor:/srv/git/" plus
ssh config for "repoor") in that example which isn't great either...
Maybe I should just use generic domains (example.com).

I'll answer to the other points in a different reply.

Michael