Re: [PATCH] git-remote: distinguish between default and configured URLs

From: John Keeping <john@keeping.me.uk>
Date: Jan 16, 2013, 10:42 UTC
Message-ID: <20130116104222.GA15125@farnsworth.metanate.com>
In-Reply-To: <a5bf3511b3ecf4e9243d550d11ab977f95ecea30.1358331096.git.git@drmicha.warpmail.net>

On Wed, Jan 16, 2013 at 11:14:48AM +0100, Michael J Gruber wrote:

Show 10 quoted lines

> The current output of "git remote -v" does not distinguish between
> explicitly configured push URLs and those coming from fetch lines.
> 
> Revise the output so so that URLs are distinguished by their labels:
> 
> (fetch): fetch config used for fetching only
> (fetch/push): fetch config used for fetching and pushing
> (fetch fallback/push): fetch config used for pushing only
> (fetch fallback): fetch config which is unused
> (push): push config used for pushing

How does this interact with url.<base>.pushInsteadOf?

I have a global rule to convert git:// URLs to ssh:// for pushing:

    [url "git@example.com:"]
        pushInsteadOf = git://example.com/

With only a URL configured for a remote (no pushURL), I get (with Git 1.8.1):

    origin git://example.com/repository.git (fetch)
    origin git@example.com:repository.git (push)

>From the original discussion in this thread, I think that if I did

"git remote set-url --add --push <url>" it would replace my current push URL, and the change to "(fetch/push)" doesn't help in this case.

Should there be special handling for pushInsteadOf here?

John