From: Michael J Gruber <git@drmicha•warpmail.net>
To: Anders Kaseorg <andersk@mit•edu>
Cc: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: [PATCH] t5516-fetch-push: Correct misspelled pushInsteadOf
Date: Wed, 04 Mar 2015 11:10:14 +0100 [thread overview]
Message-ID: <54F6DA06.7000602@drmicha.warpmail.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1503040439100.60859@buzzword-bingo.mit.edu>
Anders Kaseorg venit, vidit, dixit 04.03.2015 10:43:
> On Wed, 4 Mar 2015, Michael J Gruber wrote:
>> If there is no "pushurl":
>> "url" will be used as the "URL for fetch" and as the "URL for push".
>> if we are pushing and there is "pushinsteadof" for (part of) "url"
>> subsitute that within "url"
>> else if there is "insteadof" for (part of) "url"
>> substitute that within "url"
>>
>> If there is a "pushurl":
>> "url" will be used as the "URL for fetch" and "pushurl" as the "URL for push".
>> if we are pushing and there is "insteadof" for (part of) "pushurl"
>> substitute that within "pushurl"
>> else if we are fetching and there is "insteadof" for (part of) "url"
>> substiute that within "url"
>
> Speaking of that, I recently had to reimplement most of this logic for the
> openstack git-review tool (https://review.openstack.org/160152), which is
> why I was staring too closely at t5516 in the first place. It would be
> nice to have a ‘git ls-remote --get-push-url’ analogous to the existing
> ‘git ls-remote --get-url’.
>
> Anders
>
And vice-versa, it would be nice if "git remote" explained where the
resulting URLs come from. I vaguely remember looking into this, but I
don't think it was simple.
ls-remote and remote don't share code, which is a pitty. GSOC...
Michael
next prev parent reply other threads:[~2015-03-04 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 4:18 [PATCH] t5516-fetch-push: Correct misspelled pushInsteadOf Anders Kaseorg
2015-03-02 19:43 ` Junio C Hamano
2015-03-03 15:51 ` Michael J Gruber
2015-03-03 20:06 ` Junio C Hamano
2015-03-04 9:36 ` Michael J Gruber
2015-03-04 9:43 ` Anders Kaseorg
2015-03-04 10:10 ` Michael J Gruber [this message]
2015-03-04 20:14 ` Junio C Hamano
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=54F6DA06.7000602@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=andersk@mit$(echo .)edu \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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