On Wed, Jan 16, 2013 at 11:14:48AM +0100, Michael J Gruber wrote:
> 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:
pushInsteadOf = git://example.com/
With only a URL configured for a remote (no pushURL), I get (with Git
origin git://example.com/repository.git (fetch)
origin g...@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?
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html