From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 5/5] builtin-remote: Make "remote -v" display push urls
Date: Tue, 09 Jun 2009 11:30:27 -0700 [thread overview]
Message-ID: <7vtz2pmf98.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4A2EA04D.9080405@drmicha.warpmail.net> (Michael J. Gruber's message of "Tue\, 09 Jun 2009 19\:47\:57 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Junio C Hamano venit, vidit, dixit 09.06.2009 18:25:
>> Michael J Gruber <git@drmicha.warpmail.net> writes:
>>
>>> 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.
next prev parent reply other threads:[~2009-06-09 18:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 16:01 [PATCH 0/5] Allow push and fetch urls to be different Michael J Gruber
2009-06-09 16:01 ` [PATCH 1/5] " Michael J Gruber
2009-06-09 16:01 ` [PATCH 2/5] t5516: Check pushurl config setting Michael J Gruber
2009-06-09 16:01 ` [PATCH 3/5] technical/api-remote: Describe new struct remote member pushurl Michael J Gruber
2009-06-09 16:01 ` [PATCH 4/5] builtin-remote: Show push urls as well Michael J Gruber
2009-06-09 16:01 ` [PATCH 5/5] builtin-remote: Make "remote -v" display push urls Michael J Gruber
2009-06-09 16:25 ` Junio C Hamano
2009-06-09 17:47 ` Michael J Gruber
2009-06-09 18:30 ` Junio C Hamano [this message]
2009-06-13 16:29 ` [PATCHv2 0/5] " Michael J Gruber
2009-06-13 16:29 ` [PATCHv2 4/5] builtin-remote: Show push urls as well Michael J Gruber
2009-06-13 16:29 ` [PATCHv2 5/5] builtin-remote: Make "remote -v" display push urls Michael J Gruber
2009-06-14 5:54 ` Junio C Hamano
2009-06-09 16:25 ` [PATCH " Bert Wesarg
2009-06-09 18:07 ` Michael J Gruber
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vtz2pmf98.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).